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

google_cloudfunctions2_function allow source to be specified inline rather than bucket or repo #20739

Open
philip-harvey opened this issue Dec 18, 2024 · 0 comments
Labels

Comments

@philip-harvey
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
  • Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.
  • If an issue is assigned to a user, that user is claiming responsibility for the issue.
  • Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Description

For our deployment scenario it would be a lot simpler to have the code for the function inline vs having to make a zip file and upload it to a bucket, or to a repo.

New or Affected Resource(s)

  • google_cloudfunctions2_function

Potential Terraform Configuration

source {
      inline_source =<<EOT
import functions_framework
@functions_framework.http
def hello_get(request):
return "Hello World!"
EOT
    }

References

No response

@github-actions github-actions bot added forward/review In review; remove label to forward service/cloudfunctions labels Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant