-
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
feat: implement ec2_instance_connect_endpoint #1358
feat: implement ec2_instance_connect_endpoint #1358
Conversation
Signed-off-by: Jose Diaz-Gonzalez <[email protected]>
/test-examples="examples/ec2/v1beta1/instanceconnectendpoint.yaml" |
Thanks for the PR @josegonzalez! I kicked off the testing pipelines for you, and I can take a more detailed look tomorrow. |
@mbbush is there an easy way to see what exactly failed? There's thousands of lines of output in the logs and its not clear what I can fix :) |
From the artifacts section of https://github.com/crossplane-contrib/provider-upjet-aws/actions/runs/9493572569, download the control plane dump, and look at the logs for the provider-aws-ec2 pod in the upbound-system namespace. Here it is
This probably means that the resource you're implementing uses the terraform plugin framework, not the terraform sdk. There's a separate map to add it to at the top of externalname.go |
Hi @josegonzalez, Thank you for your effort in this PR, as @mbbush said, this is a Framework Resource, you should move the external name configuration under TerraformPluginFrameworkExternalNameConfigs. |
Sounds good! I'll get to that on thursday when I'm back at work :) |
This provider repo does not have enough maintainers to address every pull request. Since there has been no activity in the last 90 days it is now marked as |
This pull request is being closed since there has been no activity for 14 days since marking it as |
Description of your changes
This pull request implements the ec2_instance_connect_endpoint resource, allowing folks to setup EC2 Instance Connect against a given subnet. This allows for remote instance access without exposing any resources publicly or having a bastion.
https://aws.amazon.com/blogs/compute/secure-connectivity-from-public-to-private-introducing-ec2-instance-connect-endpoint-june-13-2023/
I have:
make reviewable
to ensure this PR is ready for review.backport release-x.y
labels to auto-backport this PR if necessary.How has this code been tested
I haven't tested this PR yet, wanted to know if the automated testing would pick this up or maybe get some help from folks to figure out how to get this running/tested. I'll reach out via slack tomorrow for help on the latter :)