Comments (6)
Hi @GloverChris Thank you for reporting this.
To be clear, the idea of Explicit Providers still applies to Azure, it's just that the Azure providers don't have anything like region
configuration at the moment.
Do I understand correctly that you are suggesting picking up another configuration property for this example? It might be tricky to find one that would apply consistently across many providers... Or do you have other suggestions?
from pulumi-hugo.
What I'm saying is that the region Args don't exist in the azure provider however you specify region of resources when you declare them. If you look at Virtual Network under Azure Native, you will see that you declare which region you want the Vnet there rather than having declaring the region separately as part of the provider class. This means that the azure provider has access to all regions regardless of the default region which technically makes default region declaration moot for azure projects. I hope I explained this well. 😅
Anyway I'm just saying we should call this out under explicit provider configuration in the link below as that example for declaring region for aws only applies to AWS and GCP. So best to have an "" banner stating this doesn't apply to azure in order to avoid confusion.
https://www.pulumi.com/docs/intro/concepts/resources/#explicit-provider-configuration
Hi @GloverChris Thank you for reporting this.
To be clear, the idea of Explicit Providers still applies to Azure, it's just that the Azure providers don't have anything like
region
configuration at the moment.Do I understand correctly that you are suggesting picking up another configuration property for this example? It might be tricky to find one that would apply consistently across many providers... Or do you have other suggestions?
from pulumi-hugo.
Yes, I understand all of that. Moreover, you can't set a region as a property of an explicit Azure provider.
I guess I'm failing to link this to a potential improvement in the docs. FWIW, the doc clearly uses the AWS provider and doesn't claim this example generalizes to other providers. How would you change the doc to make this more clear?
from pulumi-hugo.
Well it's in the general information section of how to use pulumi which is supposed to be agnostic to any specific language and Cloud Provider. This instead would then probably be better living in the AWS provider docs.
Yes, I understand all of that. Moreover, you can't set a region as a property of an explicit Azure provider.
I guess I'm failing to link this to a potential improvement in the docs. FWIW, the doc clearly uses the AWS provider and doesn't claim this example generalizes to other providers. How would you change the doc to make this more clear?
from pulumi-hugo.
Adding to the list for triage this week
from pulumi-hugo.
Thanks @GloverChris I know it's a long time coming but we've added more clarity to this example to help avoid the confusion you and the community noted, #3213
from pulumi-hugo.
Related Issues (20)
- Blog post on Go generics preview HOT 1
- Blog post and docs updates on importing from tfstate HOT 1
- Update What is Infrastructure As Code article HOT 2
- Identify larger assets and move them to the uploads bucket
- Get Started with Kubernetes go example fails HOT 1
- Update home page title HOT 1
- Docs on configuring policies has a code bug
- Go instructions for ECS do not compile HOT 4
- The code example is possibly outdated HOT 3
- Download & Install Pulumi ESC: "other installation methods" and "installation script" repeat once for every OS in nav HOT 3
- `brew update` is missing from ESC installation docs
- ESC CLI Login references pulumi login HOT 2
- Content Enhancement - Add Pulumi-AWS OIDC Example for Pulumi ESC
- Keycloak link in docs points to wrong URL
- ESC installation table of contents has repeated elements HOT 2
- Update .NET documentation to remove v3.1 and v5 reference, add v7. HOT 2
- poor navigation experience in the docs concept section HOT 3
- Workflow failure: Scheduled Jobs: Upgrade Examples HOT 1
- Workflow failure: Scheduled Jobs: Run Tests
- Workflow failure: Scheduled Jobs: Upgrade Examples HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pulumi-hugo.