Skip to content
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

Make backends not required on compute@edge resource #563

Merged
merged 2 commits into from
Apr 25, 2022
Merged

Make backends not required on compute@edge resource #563

merged 2 commits into from
Apr 25, 2022

Conversation

jmoney
Copy link
Contributor

@jmoney jmoney commented Apr 15, 2022

Currently, the compute@edge resource requires at least one backend to create the resource however this is actually not required of compute@edge services. Aligning the terraform resource with the compute@edge service.

Copy link
Collaborator

@Integralist Integralist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👋🏻 Thanks for opening this PR (and your patience waiting for feedback).

The changes look good to me.

I've pulled your branch locally and validated the changes manually (all works as expected).

I've also run the complete integration test suite, which passes as well.

I have only one change request, which is to update the example examples/resources/service_compute_basic_usage.tf to remove the backend block and to regenerate the docs by running make generate-docs.

Thanks!

@jmoney jmoney requested a review from Integralist April 22, 2022 22:06
@jmoney
Copy link
Contributor Author

jmoney commented Apr 22, 2022

I updated the example file and regenerated the doc

@jmoney
Copy link
Contributor Author

jmoney commented Apr 25, 2022

Let me know if anything else is required for this @Integralist

@Integralist Integralist merged commit b80ede9 into fastly:main Apr 25, 2022
@jmoney jmoney deleted the jsm.compute_backends_not_required branch April 25, 2022 12:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants