2018-06-26 20:14:03 +02:00
|
|
|
// Code generated by protoc-gen-go. DO NOT EDIT.
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
// source: analyzer.proto
|
|
|
|
|
2018-07-12 03:07:50 +02:00
|
|
|
package pulumirpc
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
|
|
|
|
import proto "github.com/golang/protobuf/proto"
|
|
|
|
import fmt "fmt"
|
|
|
|
import math "math"
|
2018-07-12 03:07:50 +02:00
|
|
|
import empty "github.com/golang/protobuf/ptypes/empty"
|
|
|
|
import _struct "github.com/golang/protobuf/ptypes/struct"
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
|
|
|
|
import (
|
|
|
|
context "golang.org/x/net/context"
|
|
|
|
grpc "google.golang.org/grpc"
|
|
|
|
)
|
|
|
|
|
|
|
|
// Reference imports to suppress errors if they are not otherwise used.
|
|
|
|
var _ = proto.Marshal
|
|
|
|
var _ = fmt.Errorf
|
|
|
|
var _ = math.Inf
|
|
|
|
|
|
|
|
// This is a compile-time assertion to ensure that this generated file
|
|
|
|
// is compatible with the proto package it is being compiled against.
|
|
|
|
// A compilation error at this line likely means your copy of the
|
|
|
|
// proto package needs to be updated.
|
|
|
|
const _ = proto.ProtoPackageIsVersion2 // please upgrade the proto package
|
|
|
|
|
2019-06-11 00:20:22 +02:00
|
|
|
// EnforcementLevel indicates the severity of a policy violation.
|
2019-06-24 02:51:15 +02:00
|
|
|
type EnforcementLevel int32
|
2019-06-11 00:20:22 +02:00
|
|
|
|
|
|
|
const (
|
2019-06-24 02:51:15 +02:00
|
|
|
EnforcementLevel_ADVISORY EnforcementLevel = 0
|
|
|
|
EnforcementLevel_MANDATORY EnforcementLevel = 1
|
2019-06-11 00:20:22 +02:00
|
|
|
)
|
|
|
|
|
2019-06-24 02:51:15 +02:00
|
|
|
var EnforcementLevel_name = map[int32]string{
|
|
|
|
0: "ADVISORY",
|
|
|
|
1: "MANDATORY",
|
2019-06-11 00:20:22 +02:00
|
|
|
}
|
2019-06-24 02:51:15 +02:00
|
|
|
var EnforcementLevel_value = map[string]int32{
|
|
|
|
"ADVISORY": 0,
|
|
|
|
"MANDATORY": 1,
|
2019-06-11 00:20:22 +02:00
|
|
|
}
|
|
|
|
|
2019-06-24 02:51:15 +02:00
|
|
|
func (x EnforcementLevel) String() string {
|
|
|
|
return proto.EnumName(EnforcementLevel_name, int32(x))
|
2019-06-11 00:20:22 +02:00
|
|
|
}
|
2019-06-24 02:51:15 +02:00
|
|
|
func (EnforcementLevel) EnumDescriptor() ([]byte, []int) {
|
2020-02-28 01:10:47 +01:00
|
|
|
return fileDescriptor_analyzer_f2f68c510282fa03, []int{0}
|
2019-06-11 00:20:22 +02:00
|
|
|
}
|
|
|
|
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
type AnalyzeRequest struct {
|
2020-02-08 01:11:34 +01:00
|
|
|
Type string `protobuf:"bytes,1,opt,name=type" json:"type,omitempty"`
|
|
|
|
Properties *_struct.Struct `protobuf:"bytes,2,opt,name=properties" json:"properties,omitempty"`
|
|
|
|
Urn string `protobuf:"bytes,3,opt,name=urn" json:"urn,omitempty"`
|
|
|
|
Name string `protobuf:"bytes,4,opt,name=name" json:"name,omitempty"`
|
|
|
|
Options *AnalyzerResourceOptions `protobuf:"bytes,5,opt,name=options" json:"options,omitempty"`
|
|
|
|
Provider *AnalyzerProviderResource `protobuf:"bytes,6,opt,name=provider" json:"provider,omitempty"`
|
|
|
|
XXX_NoUnkeyedLiteral struct{} `json:"-"`
|
|
|
|
XXX_unrecognized []byte `json:"-"`
|
|
|
|
XXX_sizecache int32 `json:"-"`
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
}
|
|
|
|
|
2018-07-12 03:07:50 +02:00
|
|
|
func (m *AnalyzeRequest) Reset() { *m = AnalyzeRequest{} }
|
|
|
|
func (m *AnalyzeRequest) String() string { return proto.CompactTextString(m) }
|
|
|
|
func (*AnalyzeRequest) ProtoMessage() {}
|
|
|
|
func (*AnalyzeRequest) Descriptor() ([]byte, []int) {
|
2020-02-28 01:10:47 +01:00
|
|
|
return fileDescriptor_analyzer_f2f68c510282fa03, []int{0}
|
2018-07-12 03:07:50 +02:00
|
|
|
}
|
|
|
|
func (m *AnalyzeRequest) XXX_Unmarshal(b []byte) error {
|
|
|
|
return xxx_messageInfo_AnalyzeRequest.Unmarshal(m, b)
|
|
|
|
}
|
|
|
|
func (m *AnalyzeRequest) XXX_Marshal(b []byte, deterministic bool) ([]byte, error) {
|
|
|
|
return xxx_messageInfo_AnalyzeRequest.Marshal(b, m, deterministic)
|
|
|
|
}
|
|
|
|
func (dst *AnalyzeRequest) XXX_Merge(src proto.Message) {
|
|
|
|
xxx_messageInfo_AnalyzeRequest.Merge(dst, src)
|
|
|
|
}
|
|
|
|
func (m *AnalyzeRequest) XXX_Size() int {
|
|
|
|
return xxx_messageInfo_AnalyzeRequest.Size(m)
|
|
|
|
}
|
|
|
|
func (m *AnalyzeRequest) XXX_DiscardUnknown() {
|
|
|
|
xxx_messageInfo_AnalyzeRequest.DiscardUnknown(m)
|
|
|
|
}
|
|
|
|
|
|
|
|
var xxx_messageInfo_AnalyzeRequest proto.InternalMessageInfo
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
|
Make more progress on the new deployment model
This change restructures a lot more pertaining to deployments, snapshots,
environments, and the like.
The most notable change is that the notion of a deploy.Source is introduced,
which splits the responsibility between the deploy.Plan -- which simply
understands how to compute and carry out deployment plans -- and the idea
of something that can produce new objects on-demand during deployment.
The primary such implementation is evalSource, which encapsulates an
interpreter and takes a package, args, and config map, and proceeds to run
the interpreter in a distinct goroutine. It synchronizes as needed to
poke and prod the interpreter along its path to create new resource objects.
There are two other sources, however. First, a nullSource, which simply
refuses to create new objects. This can be handy when writing isolated
tests but is also used to simulate the "empty" environment as necessary to
do a complete teardown of the target environment. Second, a fixedSource,
which takes a pre-computed array of objects, and hands those, in order, to
the planning engine; this is mostly useful as a testing technique.
Boatloads of code is now changed and updated in the various CLI commands.
This further chugs along towards pulumi/lumi#90. The end is in sight.
2017-06-10 20:50:47 +02:00
|
|
|
func (m *AnalyzeRequest) GetType() string {
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
if m != nil {
|
|
|
|
return m.Type
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
2018-07-12 03:07:50 +02:00
|
|
|
func (m *AnalyzeRequest) GetProperties() *_struct.Struct {
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
if m != nil {
|
|
|
|
return m.Properties
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2019-11-21 22:01:15 +01:00
|
|
|
func (m *AnalyzeRequest) GetUrn() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Urn
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzeRequest) GetName() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Name
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
2020-02-08 01:11:34 +01:00
|
|
|
func (m *AnalyzeRequest) GetOptions() *AnalyzerResourceOptions {
|
|
|
|
if m != nil {
|
|
|
|
return m.Options
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzeRequest) GetProvider() *AnalyzerProviderResource {
|
|
|
|
if m != nil {
|
|
|
|
return m.Provider
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// AnalyzerResource defines the view of a Pulumi-managed resource as sent to Analyzers. The properties
|
2019-10-25 17:29:02 +02:00
|
|
|
// of the resource are specific to the type of analysis being performed. See the Analyzer
|
|
|
|
// service definition for more information.
|
|
|
|
type AnalyzerResource struct {
|
2020-02-08 01:11:34 +01:00
|
|
|
Type string `protobuf:"bytes,1,opt,name=type" json:"type,omitempty"`
|
|
|
|
Properties *_struct.Struct `protobuf:"bytes,2,opt,name=properties" json:"properties,omitempty"`
|
|
|
|
Urn string `protobuf:"bytes,3,opt,name=urn" json:"urn,omitempty"`
|
|
|
|
Name string `protobuf:"bytes,4,opt,name=name" json:"name,omitempty"`
|
|
|
|
Options *AnalyzerResourceOptions `protobuf:"bytes,5,opt,name=options" json:"options,omitempty"`
|
|
|
|
Provider *AnalyzerProviderResource `protobuf:"bytes,6,opt,name=provider" json:"provider,omitempty"`
|
|
|
|
Parent string `protobuf:"bytes,7,opt,name=parent" json:"parent,omitempty"`
|
|
|
|
Dependencies []string `protobuf:"bytes,8,rep,name=dependencies" json:"dependencies,omitempty"`
|
|
|
|
PropertyDependencies map[string]*AnalyzerPropertyDependencies `protobuf:"bytes,9,rep,name=propertyDependencies" json:"propertyDependencies,omitempty" protobuf_key:"bytes,1,opt,name=key" protobuf_val:"bytes,2,opt,name=value"`
|
|
|
|
XXX_NoUnkeyedLiteral struct{} `json:"-"`
|
|
|
|
XXX_unrecognized []byte `json:"-"`
|
|
|
|
XXX_sizecache int32 `json:"-"`
|
2019-10-25 17:29:02 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerResource) Reset() { *m = AnalyzerResource{} }
|
|
|
|
func (m *AnalyzerResource) String() string { return proto.CompactTextString(m) }
|
|
|
|
func (*AnalyzerResource) ProtoMessage() {}
|
|
|
|
func (*AnalyzerResource) Descriptor() ([]byte, []int) {
|
2020-02-28 01:10:47 +01:00
|
|
|
return fileDescriptor_analyzer_f2f68c510282fa03, []int{1}
|
2019-10-25 17:29:02 +02:00
|
|
|
}
|
|
|
|
func (m *AnalyzerResource) XXX_Unmarshal(b []byte) error {
|
|
|
|
return xxx_messageInfo_AnalyzerResource.Unmarshal(m, b)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerResource) XXX_Marshal(b []byte, deterministic bool) ([]byte, error) {
|
|
|
|
return xxx_messageInfo_AnalyzerResource.Marshal(b, m, deterministic)
|
|
|
|
}
|
|
|
|
func (dst *AnalyzerResource) XXX_Merge(src proto.Message) {
|
|
|
|
xxx_messageInfo_AnalyzerResource.Merge(dst, src)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerResource) XXX_Size() int {
|
|
|
|
return xxx_messageInfo_AnalyzerResource.Size(m)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerResource) XXX_DiscardUnknown() {
|
|
|
|
xxx_messageInfo_AnalyzerResource.DiscardUnknown(m)
|
|
|
|
}
|
|
|
|
|
|
|
|
var xxx_messageInfo_AnalyzerResource proto.InternalMessageInfo
|
|
|
|
|
|
|
|
func (m *AnalyzerResource) GetType() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Type
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerResource) GetProperties() *_struct.Struct {
|
|
|
|
if m != nil {
|
|
|
|
return m.Properties
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2019-11-21 22:01:15 +01:00
|
|
|
func (m *AnalyzerResource) GetUrn() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Urn
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerResource) GetName() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Name
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
2020-02-08 01:11:34 +01:00
|
|
|
func (m *AnalyzerResource) GetOptions() *AnalyzerResourceOptions {
|
|
|
|
if m != nil {
|
|
|
|
return m.Options
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerResource) GetProvider() *AnalyzerProviderResource {
|
|
|
|
if m != nil {
|
|
|
|
return m.Provider
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerResource) GetParent() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Parent
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerResource) GetDependencies() []string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Dependencies
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerResource) GetPropertyDependencies() map[string]*AnalyzerPropertyDependencies {
|
|
|
|
if m != nil {
|
|
|
|
return m.PropertyDependencies
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// AnalyzerResourceOptions defines the options associated with a resource.
|
|
|
|
type AnalyzerResourceOptions struct {
|
|
|
|
Protect bool `protobuf:"varint,1,opt,name=protect" json:"protect,omitempty"`
|
|
|
|
IgnoreChanges []string `protobuf:"bytes,2,rep,name=ignoreChanges" json:"ignoreChanges,omitempty"`
|
|
|
|
DeleteBeforeReplace bool `protobuf:"varint,3,opt,name=deleteBeforeReplace" json:"deleteBeforeReplace,omitempty"`
|
|
|
|
DeleteBeforeReplaceDefined bool `protobuf:"varint,4,opt,name=deleteBeforeReplaceDefined" json:"deleteBeforeReplaceDefined,omitempty"`
|
|
|
|
AdditionalSecretOutputs []string `protobuf:"bytes,5,rep,name=additionalSecretOutputs" json:"additionalSecretOutputs,omitempty"`
|
|
|
|
Aliases []string `protobuf:"bytes,6,rep,name=aliases" json:"aliases,omitempty"`
|
|
|
|
CustomTimeouts *AnalyzerResourceOptions_CustomTimeouts `protobuf:"bytes,7,opt,name=customTimeouts" json:"customTimeouts,omitempty"`
|
|
|
|
XXX_NoUnkeyedLiteral struct{} `json:"-"`
|
|
|
|
XXX_unrecognized []byte `json:"-"`
|
|
|
|
XXX_sizecache int32 `json:"-"`
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerResourceOptions) Reset() { *m = AnalyzerResourceOptions{} }
|
|
|
|
func (m *AnalyzerResourceOptions) String() string { return proto.CompactTextString(m) }
|
|
|
|
func (*AnalyzerResourceOptions) ProtoMessage() {}
|
|
|
|
func (*AnalyzerResourceOptions) Descriptor() ([]byte, []int) {
|
2020-02-28 01:10:47 +01:00
|
|
|
return fileDescriptor_analyzer_f2f68c510282fa03, []int{2}
|
2020-02-08 01:11:34 +01:00
|
|
|
}
|
|
|
|
func (m *AnalyzerResourceOptions) XXX_Unmarshal(b []byte) error {
|
|
|
|
return xxx_messageInfo_AnalyzerResourceOptions.Unmarshal(m, b)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerResourceOptions) XXX_Marshal(b []byte, deterministic bool) ([]byte, error) {
|
|
|
|
return xxx_messageInfo_AnalyzerResourceOptions.Marshal(b, m, deterministic)
|
|
|
|
}
|
|
|
|
func (dst *AnalyzerResourceOptions) XXX_Merge(src proto.Message) {
|
|
|
|
xxx_messageInfo_AnalyzerResourceOptions.Merge(dst, src)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerResourceOptions) XXX_Size() int {
|
|
|
|
return xxx_messageInfo_AnalyzerResourceOptions.Size(m)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerResourceOptions) XXX_DiscardUnknown() {
|
|
|
|
xxx_messageInfo_AnalyzerResourceOptions.DiscardUnknown(m)
|
|
|
|
}
|
|
|
|
|
|
|
|
var xxx_messageInfo_AnalyzerResourceOptions proto.InternalMessageInfo
|
|
|
|
|
|
|
|
func (m *AnalyzerResourceOptions) GetProtect() bool {
|
|
|
|
if m != nil {
|
|
|
|
return m.Protect
|
|
|
|
}
|
|
|
|
return false
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerResourceOptions) GetIgnoreChanges() []string {
|
|
|
|
if m != nil {
|
|
|
|
return m.IgnoreChanges
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerResourceOptions) GetDeleteBeforeReplace() bool {
|
|
|
|
if m != nil {
|
|
|
|
return m.DeleteBeforeReplace
|
|
|
|
}
|
|
|
|
return false
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerResourceOptions) GetDeleteBeforeReplaceDefined() bool {
|
|
|
|
if m != nil {
|
|
|
|
return m.DeleteBeforeReplaceDefined
|
|
|
|
}
|
|
|
|
return false
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerResourceOptions) GetAdditionalSecretOutputs() []string {
|
|
|
|
if m != nil {
|
|
|
|
return m.AdditionalSecretOutputs
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerResourceOptions) GetAliases() []string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Aliases
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerResourceOptions) GetCustomTimeouts() *AnalyzerResourceOptions_CustomTimeouts {
|
|
|
|
if m != nil {
|
|
|
|
return m.CustomTimeouts
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// CustomTimeouts allows a user to be able to create a set of custom timeout parameters.
|
|
|
|
type AnalyzerResourceOptions_CustomTimeouts struct {
|
|
|
|
Create float64 `protobuf:"fixed64,1,opt,name=create" json:"create,omitempty"`
|
|
|
|
Update float64 `protobuf:"fixed64,2,opt,name=update" json:"update,omitempty"`
|
|
|
|
Delete float64 `protobuf:"fixed64,3,opt,name=delete" json:"delete,omitempty"`
|
|
|
|
XXX_NoUnkeyedLiteral struct{} `json:"-"`
|
|
|
|
XXX_unrecognized []byte `json:"-"`
|
|
|
|
XXX_sizecache int32 `json:"-"`
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerResourceOptions_CustomTimeouts) Reset() {
|
|
|
|
*m = AnalyzerResourceOptions_CustomTimeouts{}
|
|
|
|
}
|
|
|
|
func (m *AnalyzerResourceOptions_CustomTimeouts) String() string { return proto.CompactTextString(m) }
|
|
|
|
func (*AnalyzerResourceOptions_CustomTimeouts) ProtoMessage() {}
|
|
|
|
func (*AnalyzerResourceOptions_CustomTimeouts) Descriptor() ([]byte, []int) {
|
2020-02-28 01:10:47 +01:00
|
|
|
return fileDescriptor_analyzer_f2f68c510282fa03, []int{2, 0}
|
2020-02-08 01:11:34 +01:00
|
|
|
}
|
|
|
|
func (m *AnalyzerResourceOptions_CustomTimeouts) XXX_Unmarshal(b []byte) error {
|
|
|
|
return xxx_messageInfo_AnalyzerResourceOptions_CustomTimeouts.Unmarshal(m, b)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerResourceOptions_CustomTimeouts) XXX_Marshal(b []byte, deterministic bool) ([]byte, error) {
|
|
|
|
return xxx_messageInfo_AnalyzerResourceOptions_CustomTimeouts.Marshal(b, m, deterministic)
|
|
|
|
}
|
|
|
|
func (dst *AnalyzerResourceOptions_CustomTimeouts) XXX_Merge(src proto.Message) {
|
|
|
|
xxx_messageInfo_AnalyzerResourceOptions_CustomTimeouts.Merge(dst, src)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerResourceOptions_CustomTimeouts) XXX_Size() int {
|
|
|
|
return xxx_messageInfo_AnalyzerResourceOptions_CustomTimeouts.Size(m)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerResourceOptions_CustomTimeouts) XXX_DiscardUnknown() {
|
|
|
|
xxx_messageInfo_AnalyzerResourceOptions_CustomTimeouts.DiscardUnknown(m)
|
|
|
|
}
|
|
|
|
|
|
|
|
var xxx_messageInfo_AnalyzerResourceOptions_CustomTimeouts proto.InternalMessageInfo
|
|
|
|
|
|
|
|
func (m *AnalyzerResourceOptions_CustomTimeouts) GetCreate() float64 {
|
|
|
|
if m != nil {
|
|
|
|
return m.Create
|
|
|
|
}
|
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerResourceOptions_CustomTimeouts) GetUpdate() float64 {
|
|
|
|
if m != nil {
|
|
|
|
return m.Update
|
|
|
|
}
|
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerResourceOptions_CustomTimeouts) GetDelete() float64 {
|
|
|
|
if m != nil {
|
|
|
|
return m.Delete
|
|
|
|
}
|
|
|
|
return 0
|
|
|
|
}
|
|
|
|
|
|
|
|
// AnalyzerProviderResource provides information about a resource's provider.
|
|
|
|
type AnalyzerProviderResource struct {
|
|
|
|
Type string `protobuf:"bytes,1,opt,name=type" json:"type,omitempty"`
|
|
|
|
Properties *_struct.Struct `protobuf:"bytes,2,opt,name=properties" json:"properties,omitempty"`
|
|
|
|
Urn string `protobuf:"bytes,3,opt,name=urn" json:"urn,omitempty"`
|
|
|
|
Name string `protobuf:"bytes,4,opt,name=name" json:"name,omitempty"`
|
|
|
|
XXX_NoUnkeyedLiteral struct{} `json:"-"`
|
|
|
|
XXX_unrecognized []byte `json:"-"`
|
|
|
|
XXX_sizecache int32 `json:"-"`
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerProviderResource) Reset() { *m = AnalyzerProviderResource{} }
|
|
|
|
func (m *AnalyzerProviderResource) String() string { return proto.CompactTextString(m) }
|
|
|
|
func (*AnalyzerProviderResource) ProtoMessage() {}
|
|
|
|
func (*AnalyzerProviderResource) Descriptor() ([]byte, []int) {
|
2020-02-28 01:10:47 +01:00
|
|
|
return fileDescriptor_analyzer_f2f68c510282fa03, []int{3}
|
2020-02-08 01:11:34 +01:00
|
|
|
}
|
|
|
|
func (m *AnalyzerProviderResource) XXX_Unmarshal(b []byte) error {
|
|
|
|
return xxx_messageInfo_AnalyzerProviderResource.Unmarshal(m, b)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerProviderResource) XXX_Marshal(b []byte, deterministic bool) ([]byte, error) {
|
|
|
|
return xxx_messageInfo_AnalyzerProviderResource.Marshal(b, m, deterministic)
|
|
|
|
}
|
|
|
|
func (dst *AnalyzerProviderResource) XXX_Merge(src proto.Message) {
|
|
|
|
xxx_messageInfo_AnalyzerProviderResource.Merge(dst, src)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerProviderResource) XXX_Size() int {
|
|
|
|
return xxx_messageInfo_AnalyzerProviderResource.Size(m)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerProviderResource) XXX_DiscardUnknown() {
|
|
|
|
xxx_messageInfo_AnalyzerProviderResource.DiscardUnknown(m)
|
|
|
|
}
|
|
|
|
|
|
|
|
var xxx_messageInfo_AnalyzerProviderResource proto.InternalMessageInfo
|
|
|
|
|
|
|
|
func (m *AnalyzerProviderResource) GetType() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Type
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerProviderResource) GetProperties() *_struct.Struct {
|
|
|
|
if m != nil {
|
|
|
|
return m.Properties
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerProviderResource) GetUrn() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Urn
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerProviderResource) GetName() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Name
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
// AnalyzerPropertyDependencies describes the resources that a particular property depends on.
|
|
|
|
type AnalyzerPropertyDependencies struct {
|
|
|
|
Urns []string `protobuf:"bytes,1,rep,name=urns" json:"urns,omitempty"`
|
|
|
|
XXX_NoUnkeyedLiteral struct{} `json:"-"`
|
|
|
|
XXX_unrecognized []byte `json:"-"`
|
|
|
|
XXX_sizecache int32 `json:"-"`
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerPropertyDependencies) Reset() { *m = AnalyzerPropertyDependencies{} }
|
|
|
|
func (m *AnalyzerPropertyDependencies) String() string { return proto.CompactTextString(m) }
|
|
|
|
func (*AnalyzerPropertyDependencies) ProtoMessage() {}
|
|
|
|
func (*AnalyzerPropertyDependencies) Descriptor() ([]byte, []int) {
|
2020-02-28 01:10:47 +01:00
|
|
|
return fileDescriptor_analyzer_f2f68c510282fa03, []int{4}
|
2020-02-08 01:11:34 +01:00
|
|
|
}
|
|
|
|
func (m *AnalyzerPropertyDependencies) XXX_Unmarshal(b []byte) error {
|
|
|
|
return xxx_messageInfo_AnalyzerPropertyDependencies.Unmarshal(m, b)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerPropertyDependencies) XXX_Marshal(b []byte, deterministic bool) ([]byte, error) {
|
|
|
|
return xxx_messageInfo_AnalyzerPropertyDependencies.Marshal(b, m, deterministic)
|
|
|
|
}
|
|
|
|
func (dst *AnalyzerPropertyDependencies) XXX_Merge(src proto.Message) {
|
|
|
|
xxx_messageInfo_AnalyzerPropertyDependencies.Merge(dst, src)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerPropertyDependencies) XXX_Size() int {
|
|
|
|
return xxx_messageInfo_AnalyzerPropertyDependencies.Size(m)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerPropertyDependencies) XXX_DiscardUnknown() {
|
|
|
|
xxx_messageInfo_AnalyzerPropertyDependencies.DiscardUnknown(m)
|
|
|
|
}
|
|
|
|
|
|
|
|
var xxx_messageInfo_AnalyzerPropertyDependencies proto.InternalMessageInfo
|
|
|
|
|
|
|
|
func (m *AnalyzerPropertyDependencies) GetUrns() []string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Urns
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2019-10-25 17:29:02 +02:00
|
|
|
type AnalyzeStackRequest struct {
|
|
|
|
Resources []*AnalyzerResource `protobuf:"bytes,1,rep,name=resources" json:"resources,omitempty"`
|
|
|
|
XXX_NoUnkeyedLiteral struct{} `json:"-"`
|
|
|
|
XXX_unrecognized []byte `json:"-"`
|
|
|
|
XXX_sizecache int32 `json:"-"`
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzeStackRequest) Reset() { *m = AnalyzeStackRequest{} }
|
|
|
|
func (m *AnalyzeStackRequest) String() string { return proto.CompactTextString(m) }
|
|
|
|
func (*AnalyzeStackRequest) ProtoMessage() {}
|
|
|
|
func (*AnalyzeStackRequest) Descriptor() ([]byte, []int) {
|
2020-02-28 01:10:47 +01:00
|
|
|
return fileDescriptor_analyzer_f2f68c510282fa03, []int{5}
|
2019-10-25 17:29:02 +02:00
|
|
|
}
|
|
|
|
func (m *AnalyzeStackRequest) XXX_Unmarshal(b []byte) error {
|
|
|
|
return xxx_messageInfo_AnalyzeStackRequest.Unmarshal(m, b)
|
|
|
|
}
|
|
|
|
func (m *AnalyzeStackRequest) XXX_Marshal(b []byte, deterministic bool) ([]byte, error) {
|
|
|
|
return xxx_messageInfo_AnalyzeStackRequest.Marshal(b, m, deterministic)
|
|
|
|
}
|
|
|
|
func (dst *AnalyzeStackRequest) XXX_Merge(src proto.Message) {
|
|
|
|
xxx_messageInfo_AnalyzeStackRequest.Merge(dst, src)
|
|
|
|
}
|
|
|
|
func (m *AnalyzeStackRequest) XXX_Size() int {
|
|
|
|
return xxx_messageInfo_AnalyzeStackRequest.Size(m)
|
|
|
|
}
|
|
|
|
func (m *AnalyzeStackRequest) XXX_DiscardUnknown() {
|
|
|
|
xxx_messageInfo_AnalyzeStackRequest.DiscardUnknown(m)
|
|
|
|
}
|
|
|
|
|
|
|
|
var xxx_messageInfo_AnalyzeStackRequest proto.InternalMessageInfo
|
|
|
|
|
|
|
|
func (m *AnalyzeStackRequest) GetResources() []*AnalyzerResource {
|
|
|
|
if m != nil {
|
|
|
|
return m.Resources
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
Make more progress on the new deployment model
This change restructures a lot more pertaining to deployments, snapshots,
environments, and the like.
The most notable change is that the notion of a deploy.Source is introduced,
which splits the responsibility between the deploy.Plan -- which simply
understands how to compute and carry out deployment plans -- and the idea
of something that can produce new objects on-demand during deployment.
The primary such implementation is evalSource, which encapsulates an
interpreter and takes a package, args, and config map, and proceeds to run
the interpreter in a distinct goroutine. It synchronizes as needed to
poke and prod the interpreter along its path to create new resource objects.
There are two other sources, however. First, a nullSource, which simply
refuses to create new objects. This can be handy when writing isolated
tests but is also used to simulate the "empty" environment as necessary to
do a complete teardown of the target environment. Second, a fixedSource,
which takes a pre-computed array of objects, and hands those, in order, to
the planning engine; this is mostly useful as a testing technique.
Boatloads of code is now changed and updated in the various CLI commands.
This further chugs along towards pulumi/lumi#90. The end is in sight.
2017-06-10 20:50:47 +02:00
|
|
|
type AnalyzeResponse struct {
|
2019-06-11 00:20:22 +02:00
|
|
|
Diagnostics []*AnalyzeDiagnostic `protobuf:"bytes,2,rep,name=diagnostics" json:"diagnostics,omitempty"`
|
|
|
|
XXX_NoUnkeyedLiteral struct{} `json:"-"`
|
|
|
|
XXX_unrecognized []byte `json:"-"`
|
|
|
|
XXX_sizecache int32 `json:"-"`
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
}
|
|
|
|
|
2018-07-12 03:07:50 +02:00
|
|
|
func (m *AnalyzeResponse) Reset() { *m = AnalyzeResponse{} }
|
|
|
|
func (m *AnalyzeResponse) String() string { return proto.CompactTextString(m) }
|
|
|
|
func (*AnalyzeResponse) ProtoMessage() {}
|
|
|
|
func (*AnalyzeResponse) Descriptor() ([]byte, []int) {
|
2020-02-28 01:10:47 +01:00
|
|
|
return fileDescriptor_analyzer_f2f68c510282fa03, []int{6}
|
2018-07-12 03:07:50 +02:00
|
|
|
}
|
|
|
|
func (m *AnalyzeResponse) XXX_Unmarshal(b []byte) error {
|
|
|
|
return xxx_messageInfo_AnalyzeResponse.Unmarshal(m, b)
|
|
|
|
}
|
|
|
|
func (m *AnalyzeResponse) XXX_Marshal(b []byte, deterministic bool) ([]byte, error) {
|
|
|
|
return xxx_messageInfo_AnalyzeResponse.Marshal(b, m, deterministic)
|
|
|
|
}
|
|
|
|
func (dst *AnalyzeResponse) XXX_Merge(src proto.Message) {
|
|
|
|
xxx_messageInfo_AnalyzeResponse.Merge(dst, src)
|
|
|
|
}
|
|
|
|
func (m *AnalyzeResponse) XXX_Size() int {
|
|
|
|
return xxx_messageInfo_AnalyzeResponse.Size(m)
|
|
|
|
}
|
|
|
|
func (m *AnalyzeResponse) XXX_DiscardUnknown() {
|
|
|
|
xxx_messageInfo_AnalyzeResponse.DiscardUnknown(m)
|
|
|
|
}
|
|
|
|
|
|
|
|
var xxx_messageInfo_AnalyzeResponse proto.InternalMessageInfo
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
|
2019-06-11 00:20:22 +02:00
|
|
|
func (m *AnalyzeResponse) GetDiagnostics() []*AnalyzeDiagnostic {
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
if m != nil {
|
2019-06-11 00:20:22 +02:00
|
|
|
return m.Diagnostics
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2019-06-11 00:20:22 +02:00
|
|
|
type AnalyzeDiagnostic struct {
|
2019-06-24 02:51:15 +02:00
|
|
|
PolicyName string `protobuf:"bytes,1,opt,name=policyName" json:"policyName,omitempty"`
|
|
|
|
PolicyPackName string `protobuf:"bytes,2,opt,name=policyPackName" json:"policyPackName,omitempty"`
|
|
|
|
PolicyPackVersion string `protobuf:"bytes,3,opt,name=policyPackVersion" json:"policyPackVersion,omitempty"`
|
|
|
|
Description string `protobuf:"bytes,4,opt,name=description" json:"description,omitempty"`
|
|
|
|
Message string `protobuf:"bytes,5,opt,name=message" json:"message,omitempty"`
|
|
|
|
Tags []string `protobuf:"bytes,6,rep,name=tags" json:"tags,omitempty"`
|
|
|
|
EnforcementLevel EnforcementLevel `protobuf:"varint,7,opt,name=enforcementLevel,enum=pulumirpc.EnforcementLevel" json:"enforcementLevel,omitempty"`
|
2019-11-21 22:01:15 +01:00
|
|
|
Urn string `protobuf:"bytes,8,opt,name=urn" json:"urn,omitempty"`
|
2019-06-24 02:51:15 +02:00
|
|
|
XXX_NoUnkeyedLiteral struct{} `json:"-"`
|
|
|
|
XXX_unrecognized []byte `json:"-"`
|
|
|
|
XXX_sizecache int32 `json:"-"`
|
2018-07-12 03:07:50 +02:00
|
|
|
}
|
|
|
|
|
2019-06-11 00:20:22 +02:00
|
|
|
func (m *AnalyzeDiagnostic) Reset() { *m = AnalyzeDiagnostic{} }
|
|
|
|
func (m *AnalyzeDiagnostic) String() string { return proto.CompactTextString(m) }
|
|
|
|
func (*AnalyzeDiagnostic) ProtoMessage() {}
|
|
|
|
func (*AnalyzeDiagnostic) Descriptor() ([]byte, []int) {
|
2020-02-28 01:10:47 +01:00
|
|
|
return fileDescriptor_analyzer_f2f68c510282fa03, []int{7}
|
2018-07-12 03:07:50 +02:00
|
|
|
}
|
2019-06-11 00:20:22 +02:00
|
|
|
func (m *AnalyzeDiagnostic) XXX_Unmarshal(b []byte) error {
|
|
|
|
return xxx_messageInfo_AnalyzeDiagnostic.Unmarshal(m, b)
|
2018-07-12 03:07:50 +02:00
|
|
|
}
|
2019-06-11 00:20:22 +02:00
|
|
|
func (m *AnalyzeDiagnostic) XXX_Marshal(b []byte, deterministic bool) ([]byte, error) {
|
|
|
|
return xxx_messageInfo_AnalyzeDiagnostic.Marshal(b, m, deterministic)
|
2018-07-12 03:07:50 +02:00
|
|
|
}
|
2019-06-11 00:20:22 +02:00
|
|
|
func (dst *AnalyzeDiagnostic) XXX_Merge(src proto.Message) {
|
|
|
|
xxx_messageInfo_AnalyzeDiagnostic.Merge(dst, src)
|
2018-07-12 03:07:50 +02:00
|
|
|
}
|
2019-06-11 00:20:22 +02:00
|
|
|
func (m *AnalyzeDiagnostic) XXX_Size() int {
|
|
|
|
return xxx_messageInfo_AnalyzeDiagnostic.Size(m)
|
2018-07-12 03:07:50 +02:00
|
|
|
}
|
2019-06-11 00:20:22 +02:00
|
|
|
func (m *AnalyzeDiagnostic) XXX_DiscardUnknown() {
|
|
|
|
xxx_messageInfo_AnalyzeDiagnostic.DiscardUnknown(m)
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
}
|
|
|
|
|
2019-06-11 00:20:22 +02:00
|
|
|
var xxx_messageInfo_AnalyzeDiagnostic proto.InternalMessageInfo
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
|
2019-06-14 01:12:08 +02:00
|
|
|
func (m *AnalyzeDiagnostic) GetPolicyName() string {
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
if m != nil {
|
2019-06-14 01:12:08 +02:00
|
|
|
return m.PolicyName
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzeDiagnostic) GetPolicyPackName() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.PolicyPackName
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzeDiagnostic) GetPolicyPackVersion() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.PolicyPackVersion
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
2019-06-11 00:20:22 +02:00
|
|
|
func (m *AnalyzeDiagnostic) GetDescription() string {
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
if m != nil {
|
2019-06-11 00:20:22 +02:00
|
|
|
return m.Description
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
2019-06-11 00:20:22 +02:00
|
|
|
func (m *AnalyzeDiagnostic) GetMessage() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Message
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzeDiagnostic) GetTags() []string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Tags
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2019-06-24 02:51:15 +02:00
|
|
|
func (m *AnalyzeDiagnostic) GetEnforcementLevel() EnforcementLevel {
|
2019-06-11 00:20:22 +02:00
|
|
|
if m != nil {
|
|
|
|
return m.EnforcementLevel
|
|
|
|
}
|
2019-06-24 02:51:15 +02:00
|
|
|
return EnforcementLevel_ADVISORY
|
|
|
|
}
|
|
|
|
|
2019-11-21 22:01:15 +01:00
|
|
|
func (m *AnalyzeDiagnostic) GetUrn() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Urn
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
2019-06-24 02:51:15 +02:00
|
|
|
// AnalyzerInfo provides metadata about a PolicyPack inside an analyzer.
|
|
|
|
type AnalyzerInfo struct {
|
|
|
|
Name string `protobuf:"bytes,1,opt,name=name" json:"name,omitempty"`
|
|
|
|
DisplayName string `protobuf:"bytes,2,opt,name=displayName" json:"displayName,omitempty"`
|
|
|
|
Policies []*PolicyInfo `protobuf:"bytes,3,rep,name=policies" json:"policies,omitempty"`
|
2020-02-25 02:11:56 +01:00
|
|
|
Version string `protobuf:"bytes,4,opt,name=version" json:"version,omitempty"`
|
2019-06-24 02:51:15 +02:00
|
|
|
XXX_NoUnkeyedLiteral struct{} `json:"-"`
|
|
|
|
XXX_unrecognized []byte `json:"-"`
|
|
|
|
XXX_sizecache int32 `json:"-"`
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerInfo) Reset() { *m = AnalyzerInfo{} }
|
|
|
|
func (m *AnalyzerInfo) String() string { return proto.CompactTextString(m) }
|
|
|
|
func (*AnalyzerInfo) ProtoMessage() {}
|
|
|
|
func (*AnalyzerInfo) Descriptor() ([]byte, []int) {
|
2020-02-28 01:10:47 +01:00
|
|
|
return fileDescriptor_analyzer_f2f68c510282fa03, []int{8}
|
2019-06-24 02:51:15 +02:00
|
|
|
}
|
|
|
|
func (m *AnalyzerInfo) XXX_Unmarshal(b []byte) error {
|
|
|
|
return xxx_messageInfo_AnalyzerInfo.Unmarshal(m, b)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerInfo) XXX_Marshal(b []byte, deterministic bool) ([]byte, error) {
|
|
|
|
return xxx_messageInfo_AnalyzerInfo.Marshal(b, m, deterministic)
|
|
|
|
}
|
|
|
|
func (dst *AnalyzerInfo) XXX_Merge(src proto.Message) {
|
|
|
|
xxx_messageInfo_AnalyzerInfo.Merge(dst, src)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerInfo) XXX_Size() int {
|
|
|
|
return xxx_messageInfo_AnalyzerInfo.Size(m)
|
|
|
|
}
|
|
|
|
func (m *AnalyzerInfo) XXX_DiscardUnknown() {
|
|
|
|
xxx_messageInfo_AnalyzerInfo.DiscardUnknown(m)
|
|
|
|
}
|
|
|
|
|
|
|
|
var xxx_messageInfo_AnalyzerInfo proto.InternalMessageInfo
|
|
|
|
|
|
|
|
func (m *AnalyzerInfo) GetName() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Name
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerInfo) GetDisplayName() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.DisplayName
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *AnalyzerInfo) GetPolicies() []*PolicyInfo {
|
|
|
|
if m != nil {
|
|
|
|
return m.Policies
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2020-02-25 02:11:56 +01:00
|
|
|
func (m *AnalyzerInfo) GetVersion() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Version
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
2019-06-24 02:51:15 +02:00
|
|
|
// PolicyInfo provides metadata about an individual Policy within a Policy Pack.
|
|
|
|
type PolicyInfo struct {
|
|
|
|
Name string `protobuf:"bytes,1,opt,name=name" json:"name,omitempty"`
|
|
|
|
DisplayName string `protobuf:"bytes,2,opt,name=displayName" json:"displayName,omitempty"`
|
|
|
|
Description string `protobuf:"bytes,3,opt,name=description" json:"description,omitempty"`
|
|
|
|
Message string `protobuf:"bytes,4,opt,name=message" json:"message,omitempty"`
|
|
|
|
EnforcementLevel EnforcementLevel `protobuf:"varint,5,opt,name=enforcementLevel,enum=pulumirpc.EnforcementLevel" json:"enforcementLevel,omitempty"`
|
|
|
|
XXX_NoUnkeyedLiteral struct{} `json:"-"`
|
|
|
|
XXX_unrecognized []byte `json:"-"`
|
|
|
|
XXX_sizecache int32 `json:"-"`
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *PolicyInfo) Reset() { *m = PolicyInfo{} }
|
|
|
|
func (m *PolicyInfo) String() string { return proto.CompactTextString(m) }
|
|
|
|
func (*PolicyInfo) ProtoMessage() {}
|
|
|
|
func (*PolicyInfo) Descriptor() ([]byte, []int) {
|
2020-02-28 01:10:47 +01:00
|
|
|
return fileDescriptor_analyzer_f2f68c510282fa03, []int{9}
|
2019-06-24 02:51:15 +02:00
|
|
|
}
|
|
|
|
func (m *PolicyInfo) XXX_Unmarshal(b []byte) error {
|
|
|
|
return xxx_messageInfo_PolicyInfo.Unmarshal(m, b)
|
|
|
|
}
|
|
|
|
func (m *PolicyInfo) XXX_Marshal(b []byte, deterministic bool) ([]byte, error) {
|
|
|
|
return xxx_messageInfo_PolicyInfo.Marshal(b, m, deterministic)
|
|
|
|
}
|
|
|
|
func (dst *PolicyInfo) XXX_Merge(src proto.Message) {
|
|
|
|
xxx_messageInfo_PolicyInfo.Merge(dst, src)
|
|
|
|
}
|
|
|
|
func (m *PolicyInfo) XXX_Size() int {
|
|
|
|
return xxx_messageInfo_PolicyInfo.Size(m)
|
|
|
|
}
|
|
|
|
func (m *PolicyInfo) XXX_DiscardUnknown() {
|
|
|
|
xxx_messageInfo_PolicyInfo.DiscardUnknown(m)
|
|
|
|
}
|
|
|
|
|
|
|
|
var xxx_messageInfo_PolicyInfo proto.InternalMessageInfo
|
|
|
|
|
|
|
|
func (m *PolicyInfo) GetName() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Name
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *PolicyInfo) GetDisplayName() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.DisplayName
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *PolicyInfo) GetDescription() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Description
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *PolicyInfo) GetMessage() string {
|
|
|
|
if m != nil {
|
|
|
|
return m.Message
|
|
|
|
}
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *PolicyInfo) GetEnforcementLevel() EnforcementLevel {
|
|
|
|
if m != nil {
|
|
|
|
return m.EnforcementLevel
|
|
|
|
}
|
|
|
|
return EnforcementLevel_ADVISORY
|
2019-06-11 00:20:22 +02:00
|
|
|
}
|
|
|
|
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
func init() {
|
2017-09-22 04:18:21 +02:00
|
|
|
proto.RegisterType((*AnalyzeRequest)(nil), "pulumirpc.AnalyzeRequest")
|
2019-10-25 17:29:02 +02:00
|
|
|
proto.RegisterType((*AnalyzerResource)(nil), "pulumirpc.AnalyzerResource")
|
2020-02-08 01:11:34 +01:00
|
|
|
proto.RegisterMapType((map[string]*AnalyzerPropertyDependencies)(nil), "pulumirpc.AnalyzerResource.PropertyDependenciesEntry")
|
|
|
|
proto.RegisterType((*AnalyzerResourceOptions)(nil), "pulumirpc.AnalyzerResourceOptions")
|
|
|
|
proto.RegisterType((*AnalyzerResourceOptions_CustomTimeouts)(nil), "pulumirpc.AnalyzerResourceOptions.CustomTimeouts")
|
|
|
|
proto.RegisterType((*AnalyzerProviderResource)(nil), "pulumirpc.AnalyzerProviderResource")
|
|
|
|
proto.RegisterType((*AnalyzerPropertyDependencies)(nil), "pulumirpc.AnalyzerPropertyDependencies")
|
2019-10-25 17:29:02 +02:00
|
|
|
proto.RegisterType((*AnalyzeStackRequest)(nil), "pulumirpc.AnalyzeStackRequest")
|
2017-09-22 04:18:21 +02:00
|
|
|
proto.RegisterType((*AnalyzeResponse)(nil), "pulumirpc.AnalyzeResponse")
|
2019-06-11 00:20:22 +02:00
|
|
|
proto.RegisterType((*AnalyzeDiagnostic)(nil), "pulumirpc.AnalyzeDiagnostic")
|
2019-06-24 02:51:15 +02:00
|
|
|
proto.RegisterType((*AnalyzerInfo)(nil), "pulumirpc.AnalyzerInfo")
|
|
|
|
proto.RegisterType((*PolicyInfo)(nil), "pulumirpc.PolicyInfo")
|
|
|
|
proto.RegisterEnum("pulumirpc.EnforcementLevel", EnforcementLevel_name, EnforcementLevel_value)
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
// Reference imports to suppress errors if they are not otherwise used.
|
|
|
|
var _ context.Context
|
|
|
|
var _ grpc.ClientConn
|
|
|
|
|
|
|
|
// This is a compile-time assertion to ensure that this generated file
|
|
|
|
// is compatible with the grpc package it is being compiled against.
|
|
|
|
const _ = grpc.SupportPackageIsVersion4
|
|
|
|
|
2018-06-30 01:14:49 +02:00
|
|
|
// Client API for Analyzer service
|
|
|
|
|
2017-03-11 19:07:34 +01:00
|
|
|
type AnalyzerClient interface {
|
Make more progress on the new deployment model
This change restructures a lot more pertaining to deployments, snapshots,
environments, and the like.
The most notable change is that the notion of a deploy.Source is introduced,
which splits the responsibility between the deploy.Plan -- which simply
understands how to compute and carry out deployment plans -- and the idea
of something that can produce new objects on-demand during deployment.
The primary such implementation is evalSource, which encapsulates an
interpreter and takes a package, args, and config map, and proceeds to run
the interpreter in a distinct goroutine. It synchronizes as needed to
poke and prod the interpreter along its path to create new resource objects.
There are two other sources, however. First, a nullSource, which simply
refuses to create new objects. This can be handy when writing isolated
tests but is also used to simulate the "empty" environment as necessary to
do a complete teardown of the target environment. Second, a fixedSource,
which takes a pre-computed array of objects, and hands those, in order, to
the planning engine; this is mostly useful as a testing technique.
Boatloads of code is now changed and updated in the various CLI commands.
This further chugs along towards pulumi/lumi#90. The end is in sight.
2017-06-10 20:50:47 +02:00
|
|
|
// Analyze analyzes a single resource object, and returns any errors that it finds.
|
2019-10-25 17:29:02 +02:00
|
|
|
// Called with the "inputs" to the resource, before it is updated.
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
Analyze(ctx context.Context, in *AnalyzeRequest, opts ...grpc.CallOption) (*AnalyzeResponse, error)
|
2019-10-25 17:29:02 +02:00
|
|
|
// AnalyzeStack analyzes all resources within a stack, at the end of a successful
|
|
|
|
// preview or update. The provided resources are the "outputs", after any mutations
|
|
|
|
// have taken place.
|
|
|
|
AnalyzeStack(ctx context.Context, in *AnalyzeStackRequest, opts ...grpc.CallOption) (*AnalyzeResponse, error)
|
2019-06-24 02:51:15 +02:00
|
|
|
// GetAnalyzerInfo returns metadata about the analyzer (e.g., list of policies contained).
|
|
|
|
GetAnalyzerInfo(ctx context.Context, in *empty.Empty, opts ...grpc.CallOption) (*AnalyzerInfo, error)
|
2017-12-01 22:50:32 +01:00
|
|
|
// GetPluginInfo returns generic information about this plugin, like its version.
|
2018-07-12 03:07:50 +02:00
|
|
|
GetPluginInfo(ctx context.Context, in *empty.Empty, opts ...grpc.CallOption) (*PluginInfo, error)
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
}
|
|
|
|
|
2017-03-11 19:07:34 +01:00
|
|
|
type analyzerClient struct {
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
cc *grpc.ClientConn
|
|
|
|
}
|
|
|
|
|
2017-03-11 19:07:34 +01:00
|
|
|
func NewAnalyzerClient(cc *grpc.ClientConn) AnalyzerClient {
|
|
|
|
return &analyzerClient{cc}
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
}
|
|
|
|
|
2017-03-11 19:07:34 +01:00
|
|
|
func (c *analyzerClient) Analyze(ctx context.Context, in *AnalyzeRequest, opts ...grpc.CallOption) (*AnalyzeResponse, error) {
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
out := new(AnalyzeResponse)
|
2018-06-30 01:14:49 +02:00
|
|
|
err := grpc.Invoke(ctx, "/pulumirpc.Analyzer/Analyze", in, out, c.cc, opts...)
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
return out, nil
|
|
|
|
}
|
|
|
|
|
2019-10-25 17:29:02 +02:00
|
|
|
func (c *analyzerClient) AnalyzeStack(ctx context.Context, in *AnalyzeStackRequest, opts ...grpc.CallOption) (*AnalyzeResponse, error) {
|
|
|
|
out := new(AnalyzeResponse)
|
|
|
|
err := grpc.Invoke(ctx, "/pulumirpc.Analyzer/AnalyzeStack", in, out, c.cc, opts...)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
return out, nil
|
|
|
|
}
|
|
|
|
|
2019-06-24 02:51:15 +02:00
|
|
|
func (c *analyzerClient) GetAnalyzerInfo(ctx context.Context, in *empty.Empty, opts ...grpc.CallOption) (*AnalyzerInfo, error) {
|
|
|
|
out := new(AnalyzerInfo)
|
|
|
|
err := grpc.Invoke(ctx, "/pulumirpc.Analyzer/GetAnalyzerInfo", in, out, c.cc, opts...)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
return out, nil
|
|
|
|
}
|
|
|
|
|
2018-07-12 03:07:50 +02:00
|
|
|
func (c *analyzerClient) GetPluginInfo(ctx context.Context, in *empty.Empty, opts ...grpc.CallOption) (*PluginInfo, error) {
|
2017-12-01 22:50:32 +01:00
|
|
|
out := new(PluginInfo)
|
2018-06-30 01:14:49 +02:00
|
|
|
err := grpc.Invoke(ctx, "/pulumirpc.Analyzer/GetPluginInfo", in, out, c.cc, opts...)
|
2017-12-01 22:50:32 +01:00
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
return out, nil
|
|
|
|
}
|
|
|
|
|
2018-06-30 01:14:49 +02:00
|
|
|
// Server API for Analyzer service
|
|
|
|
|
2017-03-11 19:07:34 +01:00
|
|
|
type AnalyzerServer interface {
|
Make more progress on the new deployment model
This change restructures a lot more pertaining to deployments, snapshots,
environments, and the like.
The most notable change is that the notion of a deploy.Source is introduced,
which splits the responsibility between the deploy.Plan -- which simply
understands how to compute and carry out deployment plans -- and the idea
of something that can produce new objects on-demand during deployment.
The primary such implementation is evalSource, which encapsulates an
interpreter and takes a package, args, and config map, and proceeds to run
the interpreter in a distinct goroutine. It synchronizes as needed to
poke and prod the interpreter along its path to create new resource objects.
There are two other sources, however. First, a nullSource, which simply
refuses to create new objects. This can be handy when writing isolated
tests but is also used to simulate the "empty" environment as necessary to
do a complete teardown of the target environment. Second, a fixedSource,
which takes a pre-computed array of objects, and hands those, in order, to
the planning engine; this is mostly useful as a testing technique.
Boatloads of code is now changed and updated in the various CLI commands.
This further chugs along towards pulumi/lumi#90. The end is in sight.
2017-06-10 20:50:47 +02:00
|
|
|
// Analyze analyzes a single resource object, and returns any errors that it finds.
|
2019-10-25 17:29:02 +02:00
|
|
|
// Called with the "inputs" to the resource, before it is updated.
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
Analyze(context.Context, *AnalyzeRequest) (*AnalyzeResponse, error)
|
2019-10-25 17:29:02 +02:00
|
|
|
// AnalyzeStack analyzes all resources within a stack, at the end of a successful
|
|
|
|
// preview or update. The provided resources are the "outputs", after any mutations
|
|
|
|
// have taken place.
|
|
|
|
AnalyzeStack(context.Context, *AnalyzeStackRequest) (*AnalyzeResponse, error)
|
2019-06-24 02:51:15 +02:00
|
|
|
// GetAnalyzerInfo returns metadata about the analyzer (e.g., list of policies contained).
|
|
|
|
GetAnalyzerInfo(context.Context, *empty.Empty) (*AnalyzerInfo, error)
|
2017-12-01 22:50:32 +01:00
|
|
|
// GetPluginInfo returns generic information about this plugin, like its version.
|
2018-07-12 03:07:50 +02:00
|
|
|
GetPluginInfo(context.Context, *empty.Empty) (*PluginInfo, error)
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
}
|
|
|
|
|
2017-03-11 19:07:34 +01:00
|
|
|
func RegisterAnalyzerServer(s *grpc.Server, srv AnalyzerServer) {
|
|
|
|
s.RegisterService(&_Analyzer_serviceDesc, srv)
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
}
|
|
|
|
|
2017-03-11 19:07:34 +01:00
|
|
|
func _Analyzer_Analyze_Handler(srv interface{}, ctx context.Context, dec func(interface{}) error, interceptor grpc.UnaryServerInterceptor) (interface{}, error) {
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
in := new(AnalyzeRequest)
|
|
|
|
if err := dec(in); err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
if interceptor == nil {
|
2017-03-11 19:07:34 +01:00
|
|
|
return srv.(AnalyzerServer).Analyze(ctx, in)
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
}
|
|
|
|
info := &grpc.UnaryServerInfo{
|
|
|
|
Server: srv,
|
2017-09-22 04:18:21 +02:00
|
|
|
FullMethod: "/pulumirpc.Analyzer/Analyze",
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
}
|
|
|
|
handler := func(ctx context.Context, req interface{}) (interface{}, error) {
|
2017-03-11 19:07:34 +01:00
|
|
|
return srv.(AnalyzerServer).Analyze(ctx, req.(*AnalyzeRequest))
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
}
|
|
|
|
return interceptor(ctx, in, info, handler)
|
|
|
|
}
|
|
|
|
|
2019-10-25 17:29:02 +02:00
|
|
|
func _Analyzer_AnalyzeStack_Handler(srv interface{}, ctx context.Context, dec func(interface{}) error, interceptor grpc.UnaryServerInterceptor) (interface{}, error) {
|
|
|
|
in := new(AnalyzeStackRequest)
|
|
|
|
if err := dec(in); err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
if interceptor == nil {
|
|
|
|
return srv.(AnalyzerServer).AnalyzeStack(ctx, in)
|
|
|
|
}
|
|
|
|
info := &grpc.UnaryServerInfo{
|
|
|
|
Server: srv,
|
|
|
|
FullMethod: "/pulumirpc.Analyzer/AnalyzeStack",
|
|
|
|
}
|
|
|
|
handler := func(ctx context.Context, req interface{}) (interface{}, error) {
|
|
|
|
return srv.(AnalyzerServer).AnalyzeStack(ctx, req.(*AnalyzeStackRequest))
|
|
|
|
}
|
|
|
|
return interceptor(ctx, in, info, handler)
|
|
|
|
}
|
|
|
|
|
2019-06-24 02:51:15 +02:00
|
|
|
func _Analyzer_GetAnalyzerInfo_Handler(srv interface{}, ctx context.Context, dec func(interface{}) error, interceptor grpc.UnaryServerInterceptor) (interface{}, error) {
|
|
|
|
in := new(empty.Empty)
|
|
|
|
if err := dec(in); err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
if interceptor == nil {
|
|
|
|
return srv.(AnalyzerServer).GetAnalyzerInfo(ctx, in)
|
|
|
|
}
|
|
|
|
info := &grpc.UnaryServerInfo{
|
|
|
|
Server: srv,
|
|
|
|
FullMethod: "/pulumirpc.Analyzer/GetAnalyzerInfo",
|
|
|
|
}
|
|
|
|
handler := func(ctx context.Context, req interface{}) (interface{}, error) {
|
|
|
|
return srv.(AnalyzerServer).GetAnalyzerInfo(ctx, req.(*empty.Empty))
|
|
|
|
}
|
|
|
|
return interceptor(ctx, in, info, handler)
|
|
|
|
}
|
|
|
|
|
2017-12-01 22:50:32 +01:00
|
|
|
func _Analyzer_GetPluginInfo_Handler(srv interface{}, ctx context.Context, dec func(interface{}) error, interceptor grpc.UnaryServerInterceptor) (interface{}, error) {
|
2018-07-12 03:07:50 +02:00
|
|
|
in := new(empty.Empty)
|
2017-12-01 22:50:32 +01:00
|
|
|
if err := dec(in); err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
if interceptor == nil {
|
|
|
|
return srv.(AnalyzerServer).GetPluginInfo(ctx, in)
|
|
|
|
}
|
|
|
|
info := &grpc.UnaryServerInfo{
|
|
|
|
Server: srv,
|
|
|
|
FullMethod: "/pulumirpc.Analyzer/GetPluginInfo",
|
|
|
|
}
|
|
|
|
handler := func(ctx context.Context, req interface{}) (interface{}, error) {
|
2018-07-12 03:07:50 +02:00
|
|
|
return srv.(AnalyzerServer).GetPluginInfo(ctx, req.(*empty.Empty))
|
2017-12-01 22:50:32 +01:00
|
|
|
}
|
|
|
|
return interceptor(ctx, in, info, handler)
|
|
|
|
}
|
|
|
|
|
2017-03-11 19:07:34 +01:00
|
|
|
var _Analyzer_serviceDesc = grpc.ServiceDesc{
|
2017-09-22 04:18:21 +02:00
|
|
|
ServiceName: "pulumirpc.Analyzer",
|
2017-03-11 19:07:34 +01:00
|
|
|
HandlerType: (*AnalyzerServer)(nil),
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
Methods: []grpc.MethodDesc{
|
|
|
|
{
|
|
|
|
MethodName: "Analyze",
|
2017-03-11 19:07:34 +01:00
|
|
|
Handler: _Analyzer_Analyze_Handler,
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
},
|
2019-10-25 17:29:02 +02:00
|
|
|
{
|
|
|
|
MethodName: "AnalyzeStack",
|
|
|
|
Handler: _Analyzer_AnalyzeStack_Handler,
|
|
|
|
},
|
2019-06-24 02:51:15 +02:00
|
|
|
{
|
|
|
|
MethodName: "GetAnalyzerInfo",
|
|
|
|
Handler: _Analyzer_GetAnalyzerInfo_Handler,
|
|
|
|
},
|
2017-12-01 22:50:32 +01:00
|
|
|
{
|
|
|
|
MethodName: "GetPluginInfo",
|
|
|
|
Handler: _Analyzer_GetPluginInfo_Handler,
|
|
|
|
},
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
},
|
|
|
|
Streams: []grpc.StreamDesc{},
|
|
|
|
Metadata: "analyzer.proto",
|
|
|
|
}
|
|
|
|
|
2020-02-28 01:10:47 +01:00
|
|
|
func init() { proto.RegisterFile("analyzer.proto", fileDescriptor_analyzer_f2f68c510282fa03) }
|
|
|
|
|
|
|
|
var fileDescriptor_analyzer_f2f68c510282fa03 = []byte{
|
|
|
|
// 937 bytes of a gzipped FileDescriptorProto
|
|
|
|
0x1f, 0x8b, 0x08, 0x00, 0x00, 0x09, 0x6e, 0x88, 0x02, 0xff, 0xe4, 0x56, 0xcd, 0x6e, 0xdb, 0x46,
|
|
|
|
0x10, 0x36, 0x25, 0xdb, 0x92, 0x46, 0xb6, 0xa2, 0x6c, 0xda, 0x98, 0x51, 0x8c, 0xc0, 0x60, 0x8b,
|
|
|
|
0xb6, 0x28, 0x0a, 0xb9, 0x51, 0x51, 0x34, 0x2d, 0xfa, 0xe7, 0x44, 0x46, 0x10, 0x20, 0x8d, 0xd5,
|
|
|
|
0x75, 0x10, 0x34, 0x47, 0x86, 0x1c, 0xab, 0x8b, 0x50, 0x24, 0xbb, 0x5c, 0x1a, 0x50, 0x8f, 0xbd,
|
|
|
|
0xf7, 0xd0, 0x07, 0xe8, 0xad, 0x8f, 0xd0, 0x77, 0xe8, 0x0b, 0xf4, 0x81, 0xba, 0x7f, 0xa4, 0x29,
|
|
|
|
0x89, 0x52, 0x00, 0x5f, 0x7a, 0xc8, 0x6d, 0x67, 0xe6, 0x9b, 0xe1, 0xce, 0x37, 0xdf, 0xac, 0x04,
|
|
|
|
0x3d, 0x3f, 0xf6, 0xa3, 0xf9, 0xaf, 0xc8, 0x87, 0x29, 0x4f, 0x44, 0x42, 0x3a, 0x69, 0x1e, 0xe5,
|
|
|
|
0x33, 0xc6, 0xd3, 0x60, 0xb0, 0x97, 0x46, 0xf9, 0x94, 0xc5, 0x26, 0x30, 0xb8, 0x3b, 0x4d, 0x92,
|
|
|
|
0x69, 0x84, 0xc7, 0xda, 0x7a, 0x95, 0x5f, 0x1c, 0xe3, 0x2c, 0x15, 0x73, 0x1b, 0x3c, 0x5c, 0x0e,
|
|
|
|
0x66, 0x82, 0xe7, 0x81, 0x30, 0x51, 0xef, 0xb7, 0x06, 0xf4, 0x4e, 0xcc, 0x67, 0x28, 0xfe, 0x92,
|
|
|
|
0x63, 0x26, 0x08, 0x81, 0x6d, 0x31, 0x4f, 0xd1, 0x75, 0x8e, 0x9c, 0x8f, 0x3a, 0x54, 0x9f, 0xc9,
|
|
|
|
0x17, 0x00, 0x12, 0x9f, 0x22, 0x17, 0x0c, 0x33, 0xb7, 0x21, 0x23, 0xdd, 0xd1, 0xc1, 0xd0, 0x54,
|
|
|
|
0x1e, 0x16, 0x95, 0x87, 0xe7, 0xba, 0x32, 0xad, 0x40, 0x49, 0x1f, 0x9a, 0x39, 0x8f, 0xdd, 0xa6,
|
|
|
|
0xae, 0xa5, 0x8e, 0xaa, 0x7c, 0xec, 0xcf, 0xd0, 0xdd, 0x36, 0xe5, 0xd5, 0x99, 0x7c, 0x0d, 0xad,
|
|
|
|
0x24, 0x15, 0x2c, 0x89, 0x33, 0x77, 0x47, 0xd7, 0xf6, 0x86, 0x65, 0xaf, 0x43, 0x7b, 0x3d, 0x4e,
|
|
|
|
0x31, 0x4b, 0x72, 0x1e, 0xe0, 0x99, 0x41, 0xd2, 0x22, 0x85, 0x7c, 0x07, 0x6d, 0xf9, 0xc5, 0x4b,
|
|
|
|
0x16, 0x22, 0x77, 0x77, 0x75, 0xfa, 0x7b, 0x35, 0xe9, 0x13, 0x0b, 0x29, 0xca, 0xd0, 0x32, 0xc9,
|
|
|
|
0xfb, 0x73, 0x1b, 0xfa, 0xcb, 0x5f, 0x79, 0xfb, 0x68, 0x20, 0xb7, 0x61, 0x37, 0xf5, 0x39, 0xc6,
|
|
|
|
0xc2, 0x6d, 0xe9, 0x4b, 0x59, 0x8b, 0x78, 0xb0, 0x17, 0x62, 0x8a, 0x71, 0x88, 0x71, 0xa0, 0xfa,
|
|
|
|
0x6e, 0x1f, 0x35, 0x65, 0x74, 0xc1, 0x47, 0x18, 0xbc, 0x63, 0xdb, 0x9d, 0x8f, 0xab, 0xd8, 0x8e,
|
|
|
|
0xc4, 0x76, 0x47, 0x9f, 0x6f, 0xe8, 0x63, 0x38, 0xa9, 0xc9, 0x3b, 0x8d, 0x05, 0x9f, 0xd3, 0xda,
|
|
|
|
0x92, 0x83, 0x14, 0xee, 0xac, 0x4d, 0x51, 0x44, 0xbf, 0xc6, 0xb9, 0x1d, 0x9a, 0x3a, 0x92, 0x6f,
|
|
|
|
0x60, 0xe7, 0xd2, 0x8f, 0x72, 0xb4, 0xe3, 0xfa, 0xb0, 0x9e, 0x93, 0x95, 0x72, 0xd4, 0x64, 0x7d,
|
|
|
|
0xd5, 0x78, 0xe0, 0x78, 0xff, 0x36, 0xe1, 0x60, 0x0d, 0xfd, 0xc4, 0x85, 0x96, 0x1a, 0x3c, 0x06,
|
|
|
|
0x42, 0x7f, 0xb4, 0x4d, 0x0b, 0x93, 0xbc, 0x0f, 0xfb, 0x6c, 0x1a, 0x27, 0x1c, 0x1f, 0xfd, 0xec,
|
|
|
|
0xc7, 0x53, 0xad, 0x17, 0xc5, 0xdb, 0xa2, 0x93, 0x7c, 0x0a, 0xb7, 0x42, 0x8c, 0x50, 0xe0, 0x43,
|
|
|
|
0xbc, 0x90, 0x6e, 0x8a, 0x69, 0xe4, 0x07, 0xa8, 0x95, 0xd2, 0xa6, 0x75, 0x21, 0xf2, 0x2d, 0x0c,
|
|
|
|
0x6a, 0xdc, 0x63, 0xbc, 0x60, 0x31, 0x86, 0x5a, 0x4f, 0x6d, 0xba, 0x01, 0x41, 0x1e, 0xc0, 0x81,
|
|
|
|
0x1f, 0x86, 0x4c, 0x5d, 0xdf, 0x8f, 0xce, 0x31, 0xe0, 0x28, 0xce, 0x72, 0x91, 0xe6, 0x42, 0xa9,
|
|
|
|
0x4e, 0xdd, 0x70, 0x5d, 0x58, 0xf5, 0xea, 0x47, 0xcc, 0xcf, 0x64, 0x2f, 0xbb, 0x1a, 0x59, 0x98,
|
|
|
|
0xe4, 0x25, 0xf4, 0x82, 0x3c, 0x13, 0xc9, 0xec, 0x39, 0x9b, 0x61, 0xa2, 0x4a, 0xb5, 0x34, 0xdb,
|
|
|
|
0xf7, 0xdf, 0x2c, 0xe0, 0xe1, 0xa3, 0x85, 0x44, 0xba, 0x54, 0x68, 0xf0, 0x13, 0xf4, 0x16, 0x11,
|
|
|
|
0x4a, 0xa7, 0xf2, 0x56, 0xbe, 0x30, 0xbb, 0xe9, 0x50, 0x6b, 0x29, 0x7f, 0x9e, 0x86, 0xca, 0xdf,
|
|
|
|
0x30, 0x7e, 0x63, 0x29, 0xbf, 0xa1, 0x43, 0xb3, 0x2a, 0xfd, 0xc6, 0xf2, 0x7e, 0x77, 0xc0, 0x5d,
|
|
|
|
0xb7, 0x16, 0xff, 0xc3, 0xfa, 0x7b, 0x23, 0x38, 0xdc, 0xa4, 0x48, 0x95, 0x23, 0x53, 0x33, 0x79,
|
|
|
|
0x25, 0xc5, 0xbd, 0x3e, 0x7b, 0x13, 0xb8, 0x65, 0x73, 0xce, 0x85, 0x1f, 0xbc, 0x2e, 0xde, 0xf0,
|
|
|
|
0x2f, 0xa1, 0xc3, 0x6d, 0x27, 0x06, 0xdf, 0x1d, 0xdd, 0xdd, 0x30, 0x0a, 0x7a, 0x85, 0xf6, 0x7e,
|
|
|
|
0x84, 0x1b, 0xe5, 0x0f, 0x42, 0x96, 0xca, 0x01, 0x29, 0xc5, 0x75, 0x43, 0xe6, 0x4b, 0xd9, 0x66,
|
|
|
|
0x82, 0x05, 0x46, 0xc7, 0xdd, 0xd1, 0xe1, 0x6a, 0xbd, 0x71, 0x09, 0xa2, 0xd5, 0x04, 0xef, 0xef,
|
|
|
|
0x06, 0xdc, 0x5c, 0x81, 0x90, 0x7b, 0x92, 0xcd, 0x24, 0x62, 0xc1, 0xfc, 0x99, 0x22, 0xc2, 0xf0,
|
|
|
|
0x5c, 0xf1, 0x90, 0x0f, 0xa0, 0x67, 0xac, 0x89, 0x6c, 0x4c, 0x63, 0x1a, 0x1a, 0xb3, 0xe4, 0x25,
|
|
|
|
0x9f, 0xc0, 0xcd, 0x2b, 0xcf, 0x0b, 0xe4, 0x99, 0x54, 0x95, 0xa5, 0x7a, 0x35, 0x40, 0x8e, 0x64,
|
|
|
|
0x2f, 0x98, 0x05, 0x9c, 0x69, 0xf5, 0x59, 0xfe, 0xab, 0x2e, 0xa5, 0xf2, 0x19, 0x66, 0x99, 0x3f,
|
|
|
|
0x45, 0xfd, 0x0a, 0x4b, 0x95, 0x5b, 0x53, 0x6b, 0xc2, 0x9f, 0x16, 0xe2, 0xd7, 0x67, 0xf2, 0x18,
|
|
|
|
0xfa, 0x18, 0xcb, 0x2d, 0x0b, 0x70, 0x26, 0xdf, 0xca, 0xa7, 0x78, 0x89, 0x91, 0xd6, 0x7e, 0x6f,
|
|
|
|
0x81, 0xf0, 0xd3, 0x25, 0x08, 0x5d, 0x49, 0x2a, 0x34, 0xd2, 0x2e, 0x35, 0xe2, 0xfd, 0xe1, 0xc0,
|
|
|
|
0x5e, 0x31, 0xa9, 0x27, 0x12, 0x5e, 0x8a, 0xc6, 0xa9, 0xfc, 0x66, 0xa8, 0x7e, 0x58, 0x26, 0x17,
|
|
|
|
0x7c, 0x5e, 0xa1, 0xa8, 0xea, 0x22, 0xf7, 0xe5, 0xef, 0x82, 0xa2, 0x41, 0x69, 0xb6, 0xa9, 0x47,
|
|
|
|
0xf7, 0x6e, 0xe5, 0x66, 0x13, 0xcd, 0x90, 0x2a, 0x4f, 0x4b, 0x98, 0xa2, 0xe0, 0xd2, 0x12, 0x69,
|
|
|
|
0x08, 0x2a, 0x4c, 0xef, 0x1f, 0x07, 0xe0, 0x2a, 0xe5, 0x9a, 0x37, 0x5a, 0x9a, 0x41, 0x73, 0xe3,
|
|
|
|
0x0c, 0xb6, 0x17, 0x67, 0x50, 0xc7, 0xf7, 0xce, 0x35, 0xf8, 0xfe, 0xf8, 0x18, 0xfa, 0xcb, 0x28,
|
|
|
|
0xb2, 0x07, 0xed, 0x93, 0xf1, 0x8b, 0x27, 0xe7, 0x67, 0xf4, 0x65, 0x7f, 0x8b, 0xec, 0x43, 0xe7,
|
|
|
|
0x87, 0x93, 0x67, 0xe3, 0x93, 0xe7, 0xca, 0x74, 0x46, 0x7f, 0x35, 0x64, 0xd4, 0x8e, 0x83, 0x3c,
|
|
|
|
0x84, 0x96, 0x3d, 0x93, 0x3b, 0xab, 0x8b, 0x60, 0xd7, 0x70, 0x30, 0xa8, 0x0b, 0x99, 0xa5, 0xf2,
|
|
|
|
0xb6, 0xc8, 0xd3, 0x72, 0xbc, 0x7a, 0x77, 0xc9, 0xbd, 0x55, 0x74, 0x75, 0xa9, 0xdf, 0x50, 0x6d,
|
|
|
|
0x0c, 0x37, 0x1e, 0xa3, 0x58, 0xd0, 0xcb, 0xed, 0x95, 0xb7, 0xe9, 0x54, 0xfd, 0x31, 0x1c, 0x1c,
|
|
|
|
0xd4, 0x3c, 0x05, 0x2a, 0x41, 0x56, 0xf9, 0x1e, 0xf6, 0x65, 0x95, 0x89, 0xfe, 0x77, 0xb9, 0xb1,
|
|
|
|
0xc6, 0x82, 0x86, 0x4a, 0xb8, 0xb7, 0xf5, 0x6a, 0x57, 0x03, 0x3f, 0xfb, 0x2f, 0x00, 0x00, 0xff,
|
|
|
|
0xff, 0xad, 0x65, 0xec, 0xfa, 0xbe, 0x0a, 0x00, 0x00,
|
Add basic analyzer support
This change introduces the basic requirements for analyzers, as per
pulumi/coconut#119. In particular, an analyzer can implement either,
or both, of the RPC methods, Analyze and AnalyzeResource. The former
is meant to check an overall deployment (e.g., to ensure it has been
signed off on) and the latter is to check individual resources (e.g.,
to ensure properties of them are correct, such as checking style,
security, etc. rules). These run simultaneous to overall checking.
Analyzers are loaded as plugins just like providers are. The difference
is mainly in their naming ("analyzer-" prefix, rather than "resource-"),
and the RPC methods that they support.
This isn't 100% functional since we need a way to specify at the CLI
that a particular analyzer should be run, in addition to a way of
recording which analyzers certain projects should use in their manifests.
2017-03-11 08:49:17 +01:00
|
|
|
}
|