4 ms·
Looks very interesting. I have a couple of questions: 1. One of my pet peeves with CloudFormation is the disconnect between the state of CF and the "actual" st
by digitalsanctum 8y ago
Looks very interesting. I have a couple of questions:
1. One of my pet peeves with CloudFormation is the disconnect between the state of CF and the "actual" state if someone decides to update resources by not using CF. Does Pulumi do checks to verify that the actual state matches its assumed state?
2. Is there a guide for contributing a new language and/or provider?
Also, I tried getting an invite for the Pulumi Slack community and was greeted with "invite_limit_reached".
- lindydonna 8y ago> Also, I tried getting an invite for the Pulumi Slack community and was greeted with "invite_limit_reached". We're hitting Slack's rate limiting on invites. Please DM your email @PulumiCorp on Twitter and we'll get you added!
- elcritch 8y agoI’d like to know the answer to that as well... Error handling semantics across languages vary greatly. Does the user code need to handle errors or mismatched state or does Pulumi? If Pulumi does how do you get/ report errors?
- swgillespie 8y ago[Disclosure - I'm a Pulumi employee] There is a top-level CLI verb called `refresh` that explicitly checks Pulumi's idea of the state of the world against the actual state of the world. If there's a diff, Pulumi reconciles the diff by updating its own state. `pulumi update` does not do this by default, but you can run `pulumi refresh` at any time to verify that your state has not drifted from reality.