-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consume StateFunc fix #1188
Consume StateFunc fix #1188
Conversation
8641ad0
to
5e62c84
Compare
/test-examples="examples/iam/v1beta1/policy.yaml" |
/test-examples="examples/iam/v1beta1/rolepolicy.yaml" |
Signed-off-by: Sergen Yalçın <[email protected]>
5e62c84
to
2ca6cdf
Compare
/test-examples="examples/iam/v1beta1/policy.yaml" |
/test-examples="examples/iam/v1beta1/rolepolicy.yaml" |
/test-examples="examples/apigateway/v1beta1/integrationresponse.yaml" |
/test-examples="examples/appsync/v1beta1/datasource.yaml" |
/test-examples="examples/batch/v1beta1/jobdefinition.yaml" |
/test-examples="examples/cloudformation/v1beta1/stack.yaml" |
/test-examples="examples/cloudwatch/v1beta1/dashboard.yaml" |
/test-examples="examples/codecommit/v1beta1/approvalruletemplateassociation.yaml" |
/test-examples="examples/connect/v1beta1/contactflow.yaml" |
/test-examples="examples/connect/v1beta1/contactflowmodule.yaml" |
/test-examples="examples/ecr/v1beta1/lifecyclepolicy.yaml" |
/test-examples="examples/ecr/v1beta1/registrypolicy.yaml" |
/test-examples="examples/ecr/v1beta1/repositorypolicy.yaml" |
/test-examples="examples/ecrpublic/v1beta1/repositorypolicy.yaml" |
/test-examples="examples/ecs/v1beta1/taskdefinition.yaml" |
/test-examples="examples/elasticache/v1beta1/parametergroup.yaml" |
/test-examples="examples/elasticache/v1beta1/subnetgroup.yaml" |
/test-examples="examples/elasticsearch/v1beta1/domainpolicy.yaml" |
/test-examples="examples/elbv2/v1beta1/lblistener.yaml" |
/test-examples="examples/emrserverless/v1beta1/application.yaml" |
/test-examples="examples/evidently/v1beta1/segment.yaml" |
/test-examples="examples/firehose/v1beta1/deliverystream.yaml" |
/test-examples="examples/glacier/v1beta1/vaultlock.yaml" |
/test-examples="examples/iot/v1beta1/policy.yaml" |
/test-examples="examples/rds/v1beta1/instance.yaml" |
/test-examples="examples/waf/v1beta1/regexmatchset.yaml" |
/test-examples="examples/apigateway/v1beta1/integrationresponse.yaml" |
/test-examples="examples/rds/v1beta1/instance.yaml" |
5a9d821
to
85a9d37
Compare
/test-examples="examples/apigateway/v1beta1/integrationresponse.yaml" |
85a9d37
to
4249af5
Compare
/test-examples="examples/apigateway/v1beta1/integrationresponse.yaml" |
- apigateway.IntegrationResponse - rds.v1beta1.Instance - rds.v1beta2.Instance Signed-off-by: Sergen Yalçın <[email protected]>
4249af5
to
7102740
Compare
/test-examples="examples/apigateway/v1beta1/integrationresponse.yaml" |
- docdb.ClusterInstance - elasticache.Cluster - elasticache.ReplicationGroup Signed-off-by: Sergen Yalçın <[email protected]>
/test-examples="examples/elasticache/v1beta1/cluster.yaml" |
/test-examples="examples/elasticache/v1beta2/replicationgroup.yaml" |
/test-examples="examples/docdb/v1beta1/clusterinstance.yaml" |
/test-examples="examples/wafregional/v1beta1/regexmatchset.yaml" |
Signed-off-by: Sergen Yalçın <[email protected]>
/test-examples="examples/iam/v1beta1/policy.yaml" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @sergenyalcin, lgtm. And special thanks for all the example manifest fixes/improvements here!
@@ -13,6 +13,8 @@ spec: | |||
apiVersion: apigateway.aws.upbound.io/v1beta1 | |||
kind: IntegrationResponse | |||
metadata: | |||
annotations: | |||
uptest.upbound.io/disable-import: "true" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we disable the import tests? A comment may help for these dependencies. Is it because we just want to test importing the main resource and not interested in importing the dependencies? If so, we may also consider running the import tests only for the main resources in the example manifests so that we don't need to disable the import tests for each of the dependencies, what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added comment to the example manifest. As you know, for the update step we do this. I mean, we only execute the update step for the root resources. For import statement we may also consider executing this step on the root resource of the example manifest.
Signed-off-by: Sergen Yalçın <[email protected]>
Description of your changes
This PR consumes the StateFunc fix in upjet. For more details please see: crossplane/upjet#358
I have:
make reviewable test
to ensure this PR is ready for review.How has this code been tested
Uptest
Manual