Highlights
- Arctic Code Vault Contributor
Create your own GitHub profile
Sign up for your own profile on GitHub, the best place to host code, manage projects, and build software alongside 50 million developers.
Sign up
Popular repositories
-
TeamCitySharp Archived
No Longer Maintained - please use https://github.com/mavezeau/TeamCitySharp
-
-
-
-
9,786 contributions in the last year
Activity overview
Contribution activity
October 2020
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 33 repositories not shown
Created a pull request in pulumi/pulumi-kubernetes that received 10 comments
Ignore Annotations rather than delete them from the metadata
This seems to be a more rounded behaviour
- Upgrade to Pulumi v2.12.0 and pulumi-terraform-bridge v2.11.0
- Upgrade to v3.11.0 of the AWS Terraform Provider
- Upgrade to v3.10.0 of the AWS Terraform Provider
- Upgrade to pulumi-terraform-bridge v2.11.0
- Upgrade to v2.10.4 pulumi-terraform-bridge to fix a regression on pulumi config set
- Revert to pulumi-terraform-bridge v2.9.2
- Fixup the AWS Batch Compute Environment example
- Disable Autonaming on directoryservice.Directory
- Upgrade to v3.9.0 of the AWS Terraform Provider
- Migrate to use git sha of non-official GHAs
- Upgrade to Pulumi v2.10.2 and pulumi-terraform-bridge v2.10.2
- Ensure CLI doesn't panic when pulumi watch is used with policies enabled
- Reintroduce the GOPATH env in windows master build
- Add the ability to specify privateKey contents to AutomationAPI
- Accept `-f` as a shorthand for `--skip-preview` on `up`, `refresh` and `destroy` operations
- Cleanup Windows builds and move windows release build back to GitHub Actions
- Validate and error on invalid cloudUrl formats on pulumi login
- Respect logging verbosity as part of pulumi plugin install
- Protect against panic in finding go executable and finding resources
- Improve user message when pulumi plugin rm --all has no plugins to remove
- Ensure secret provider variables are cleaned up when changing secret providers
- Reorder resource docs templates to make deprecated more prominent
- Upgrade to Pulumi v2.12.0 and pulumi-terraform-bridge v2.11.0
- Upgrade to v2.32.0 of the AzureRM Terraform Provider
- Upgrade to v2.31.1 of the AzureRM Terraform Provider
- Upgrade to v2.10.4 pulumi-terraform-bridge to fix a regression on pulumi config set
- Disable autonaming for 'mysql.Configuration', 'mariadb.Configuration' and 'postgres.Configuration'
- Migrate to use git sha of non-official GHAs
- Upgrade to v2.30.0 of the AzureRM Terraform Provider
- Migrate to the new TF Shim functionality as a precursor to tf-plugin-sdk upgrade
- Upgrade to v1.101.0 of the AliCloud Terraform Provider
- Upgrade to Pulumi v2.12.0 and pulumi-terraform-bridge v2.11.0
- Migrate to the new TF Shim functionality as a precursor to provider upgrades
- Upgrade to v1.100.1 of the AliCloud Terraform Provider
- Upgrade to v1.100.0 of the AliCloud Terraform Provider
- Migrate to use git sha of non-official GHAs
- Upgrade to v2.13.0 of the NewRelic Terraform Provider
- Upgrade to Pulumi v2.12.0 and pulumi-terraform-bridge v2.11.0
- Upgrade to pulumi v2.11.2 and pulumi-terraform-bridge v2.11.0
- Migrate to use git sha of non-official GHAs
- Upgrade to v2.12.0 of the NewRelic Terraform Provider
- Upgrade to v2.8.0 of the NewRelic Terraform Provider
- Fix typo
- add docs build
- Regen docs pulumi@2.12.0
- Regen docs azure@v3.25.0
- Regen docs alicloud@v2.21.1
- Regen docs digitalocean@v2.9.0
- Regen docs newrelic@v3.6.0
- Regen docs alicloud@v2.21.0
- Regen docs aws@v3.7.0
- Regen docs aiven@v3.1.5
- Regen docs github@v2.1.0
- Regen docs okta@v2.4.2
- Update Pulumi Managed Backend and Self-managed backend
- Regen docs okta@v2.4.1
- Regen docs okta@v2.4.0
- Regen docs linode@v2.6.2
- Regen docs aws@v3.6.1
- Regen docs azure@v3.24.1
- Update Azure NextGen API docs to 0.2.1
- Regen docs aws@v3.6.0
- Regen docs docker@v2.3.1
- install pulumictl for some docs builds
- Regen docs wavefront@v0.4.0
- Regen docs hcloud@v0.3.0
- Regen docs openstack@v2.7.0
- Some pull request reviews not shown.
Created an issue in cloudflare/terraform-provider-cloudflare that received 5 comments
Creation of CAA records
Hi, I am investigating the creation of CAA records with this Terraform Provider. It was suggested this was added in #97 where I could specify this …
- Upgrade to v2.13.0 of the NewRelic Terraform Provider
- Upgrade to v2.12.1 of the NewRelic Terraform Provider
- Upgrade to v2.12.0 of the NewRelic Terraform Provider
- Upgrade to v2.11.1 of the NewRelic Terraform Provider
- Upgrade to v2.11.0 of the NewRelic Terraform Provider
- Upgrade to v2.10.3 of the NewRelic Terraform Provider
- Upgrade to v2.10.0 of the NewRelic Terraform Provider
- Upgrade to v2.9.0 of the NewRelic Terraform Provider
- Upgrade to v2.8.0 of the NewRelic Terraform Provider