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

New Type Mappings + Default ID Generator #3

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

Shrooblord
Copy link
Contributor

Hi there!

I've been using this tool to import resources from our GCP into Pulumi. In the process, I defined new resource type mappings and found out the correct syntax for them for Pulumi to accept the configuration. Note that ContainerCluster suffers from an import bug on Pulumi's side as far as I can tell; it does not seem solvable through this tool alone.

Further, I split off two resource types into a new broken_types object, which does not get used to populate the import JSON. The LoggingLogSink from the original codebase was moved there, as well as another resource ComputeBackendService, which I was also unable to defined the correct syntax for so GCP wouldn't return "this resource doesn't exist". From my work on the other resource types, I expect this to be a 'simple' case of properly defining the URI to the actual resource; but I wasn't able to track this definition down for the resources under broken_types.

Additionally, I added a function to generate a resourceID for resources that don't define one themselves in the YAML output from config-connector. E.g. IAMPolicyMember resources don't define a resourceID out-of-the-box.

P.S.
I tried to rebase and clean up my commits but the commit history in this PR refuses to accept my efforts when it comes to the commits made on 11th of August (8dac1f8, ab4ee52 and d46bbd4) and the first one from Aug 15th (086da78), even though those are superseded by / made irrelevant by the later commits... blame it on my (lack of) git-fu 🙈

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.

1 participant