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

Add notification configuration #28

Open
KishoreNamala opened this issue Dec 9, 2019 · 6 comments
Open

Add notification configuration #28

KishoreNamala opened this issue Dec 9, 2019 · 6 comments
Labels
enhancement New feature or request P3 medium priority issues triaged Scoped and ready for work

Comments

@KishoreNamala
Copy link

Hi,

Any plans to include notification configuration on the bucket in this module anytime soon ? I currently use this module and wondering if there's a way to do the notifications independently and still use this module...should I do this after the bucket is created by using a depends-on ?

I can try taking this up, but don't know where to get started for working as a contributor.

Thanks
Kishore

@morgante morgante changed the title notification configuration Add notification configuration Dec 9, 2019
@morgante
Copy link
Contributor

morgante commented Dec 9, 2019

We could certainly add it, if you'd be willing to take this on it'd be great. This explains how to set up tests and such, then you could just add a new notifications variable to the module.

Based on that variable, it should create the required google_storage_notification resources.

@KishoreNamala
Copy link
Author

KishoreNamala commented Jan 12, 2020

We could certainly add it, if you'd be willing to take this on it'd be great. This explains how to set up tests and such, then you could just add a new notifications variable to the module.

Based on that variable, it should create the required google_storage_notification resources.

can you clarify a bit more on this test environment section in set up

I don't have permissions at the folder level. So, what's my alternative here ?

@morgante
Copy link
Contributor

If you don't have permission to create projects yourself, you can also reuse an existing project. You'll simply need to manually create a test/setup.sh file which includes content like:

export TF_VAR_project_id='my-project-id'
export SERVICE_ACCOUNT_JSON='my-sa-json'

See this file for more details: https://github.com/terraform-google-modules/terraform-google-cloud-storage/blob/master/test/setup/make_source.sh

@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Jan 20, 2021
@KishoreNamala
Copy link
Author

I'll be getting back to this one soon.

@github-actions github-actions bot removed the Stale label Jan 25, 2021
@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Mar 27, 2021
@morgante morgante added enhancement New feature or request P3 medium priority issues triaged Scoped and ready for work and removed Stale labels Mar 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P3 medium priority issues triaged Scoped and ready for work
Projects
None yet
2 participants