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

Configure _iam_binding and _iam_policy resources #10

Closed
AaronME opened this issue Aug 22, 2022 · 2 comments
Closed

Configure _iam_binding and _iam_policy resources #10

AaronME opened this issue Aug 22, 2022 · 2 comments

Comments

@AaronME
Copy link
Contributor

AaronME commented Aug 22, 2022

Pending resolution of #14 we are collecting questionable resources here:

External name configuration of 9 resources in the iap group:

(Extracted from upbound/official-providers#281)

External name configuration of 2 resources in the storage group:

(Extracted from upbound/official-providers#444)

External name configuration of 2 resources in the secretmanager group:

External name configuration of 2 resources in the sourcerepo group:

External name configuration of 4 resources in the spanner group:

(Extracted from upbound/official-providers#284)

External name configuration of 2 resources in the notebooks group:

External name configuration of 1 resources in the orgpolicy group:

External name configuration of 4 resources in the privateca group:

(Extracted from upbound/official-providers#283)

External name configuration of 1 resources in the notebooks group:

(Extracted from #17)

External name configuration of resources in the compute group:

(Extracted from #18)

External name configuration of resources in the iap group:

External name configuration of resources in the healthcare group:

@jeanduplessis jeanduplessis transferred this issue from another repository Oct 10, 2022
Copy link

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

@github-actions github-actions bot added the stale label Apr 21, 2024
Copy link

github-actions bot commented May 5, 2024

This issue is being closed since there has been no activity for 14 days since marking it as stale. If you still need help, feel free to comment or reopen the issue!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants