sdkgen

sdk/dotnet/Yaml/V2/ConfigFile.cs

@@ -12,6 +12,39 @@ namespace Pulumi.Kubernetes.Yaml.V2
     /// <summary>
     /// ConfigFile creates a set of Kubernetes resources from a Kubernetes YAML file.
     /// 
+    /// ## Dependency ordering
+    /// Sometimes resources must be applied in a specific order. For example, a namespace resource must be
+    /// created before any namespaced resources, or a Custom Resource Definition (CRD) must be pre-installed.
+    /// 
+    /// Pulumi uses heuristics to determine which order to apply and delete objects within the ConfigFile.  Pulumi also
+    /// waits for each object to be fully reconciled, unless `skipAwait` is enabled.
+    /// 
+    /// ### Explicit Dependency Ordering
+    /// Pulumi supports the `config.kubernetes.io/depends-on` annotation to declare an explicit dependency a given resource.
+    /// The annotation accepts a list of resource references, delimited by commas.
+    /// 
+    /// Note that references to resources outside the ConfigFile aren't supported.
+    /// 
+    /// **Resource reference**
+    /// 
+    /// A resource reference is a string that uniquely identifies a resource.
+    /// 
+    /// It consists of the group, kind, name, and optionally the namespace, delimited by forward slashes.
+    /// 
+    /// | Resource Scope   | Format                                         |
+    /// | :--------------- | :--------------------------------------------- |
+    /// | namespace-scoped | `&lt;group&gt;/namespaces/&lt;namespace&gt;/&lt;kind&gt;/&lt;name&gt;` |
+    /// | cluster-scoped   | `&lt;group&gt;/&lt;kind&gt;/&lt;name&gt;`                        |
+    /// 
+    /// For resources in the “core” group, the empty string is used instead (for example: `/namespaces/test/Pod/pod-a`).
+    /// 
+    /// ### Ordering across ConfigFiles
+    /// The `dependsOn` resource option creates a list of explicit dependencies between Pulumi resources.
+    /// Make another resource dependent on the ConfigFile to wait for the resources within the group to be deployed.
+    /// 
+    /// A best practice is to deploy each application using its own ConfigFile, especially when that application
+    /// installs custom resource definitions.
+    /// 
     /// ## Example Usage
     /// ### Local File
     /// ```csharp

sdk/dotnet/Yaml/V2/ConfigGroup.cs

@@ -18,6 +18,39 @@ namespace Pulumi.Kubernetes.Yaml.V2
     /// 3. Using a literal string containing YAML, or a list of such strings:
     /// 4. Any combination of files, patterns, or YAML strings:
     /// 
+    /// ## Dependency ordering
+    /// Sometimes resources must be applied in a specific order. For example, a namespace resource must be
+    /// created before any namespaced resources, or a Custom Resource Definition (CRD) must be pre-installed.
+    /// 
+    /// Pulumi uses heuristics to determine which order to apply and delete objects within the ConfigGroup.  Pulumi also
+    /// waits for each object to be fully reconciled, unless `skipAwait` is enabled.
+    /// 
+    /// ### Explicit Dependency Ordering
+    /// Pulumi supports the `config.kubernetes.io/depends-on` annotation to declare an explicit dependency a given resource.
+    /// The annotation accepts a list of resource references, delimited by commas.
+    /// 
+    /// Note that references to resources outside the ConfigGroup aren't supported.
+    /// 
+    /// **Resource reference**
+    /// 
+    /// A resource reference is a string that uniquely identifies a resource.
+    /// 
+    /// It consists of the group, kind, name, and optionally the namespace, delimited by forward slashes.
+    /// 
+    /// | Resource Scope   | Format                                         |
+    /// | :--------------- | :--------------------------------------------- |
+    /// | namespace-scoped | `<group>/namespaces/<namespace>/<kind>/<name>` |
+    /// | cluster-scoped   | `<group>/<kind>/<name>`                        |
+    /// 
+    /// For resources in the “core” group, the empty string is used instead (for example: `/namespaces/test/Pod/pod-a`).
+    /// 
+    /// ### Ordering across ConfigGroups
+    /// The `dependsOn` resource option creates a list of explicit dependencies between Pulumi resources.
+    /// Make another resource dependent on the ConfigGroup to wait for the resources within the group to be deployed.
+    /// 
+    /// A best practice is to deploy each application using its own ConfigGroup, especially when that application
+    /// installs custom resource definitions.
+    /// 
     /// ## Example Usage
     /// ### Local File
     /// ```csharp

sdk/java/src/main/java/com/pulumi/kubernetes/yaml/v2/ConfigFile.java

@@ -17,6 +17,39 @@
 /**
  * ConfigFile creates a set of Kubernetes resources from a Kubernetes YAML file.
  * 
+ * ## Dependency ordering
+ * Sometimes resources must be applied in a specific order. For example, a namespace resource must be
+ * created before any namespaced resources, or a Custom Resource Definition (CRD) must be pre-installed.
+ * 
+ * Pulumi uses heuristics to determine which order to apply and delete objects within the ConfigFile.  Pulumi also
+ * waits for each object to be fully reconciled, unless `skipAwait` is enabled.
+ * 
+ * ### Explicit Dependency Ordering
+ * Pulumi supports the `config.kubernetes.io/depends-on` annotation to declare an explicit dependency a given resource.
+ * The annotation accepts a list of resource references, delimited by commas.
+ * 
+ * Note that references to resources outside the ConfigFile aren't supported.
+ * 
+ * **Resource reference**
+ * 
+ * A resource reference is a string that uniquely identifies a resource.
+ * 
+ * It consists of the group, kind, name, and optionally the namespace, delimited by forward slashes.
+ * 
+ * | Resource Scope   | Format                                         |
+ * | :--------------- | :--------------------------------------------- |
+ * | namespace-scoped | `<group>/namespaces/<namespace>/<kind>/<name>` |
+ * | cluster-scoped   | `<group>/<kind>/<name>`                        |
+ * 
+ * For resources in the “core” group, the empty string is used instead (for example: `/namespaces/test/Pod/pod-a`).
+ * 
+ * ### Ordering across ConfigFiles
+ * The `dependsOn` resource option creates a list of explicit dependencies between Pulumi resources.
+ * Make another resource dependent on the ConfigFile to wait for the resources within the group to be deployed.
+ * 
+ * A best practice is to deploy each application using its own ConfigFile, especially when that application
+ * installs custom resource definitions.
+ * 
  * ## Example Usage
  * {% /examples %}}
  * 

sdk/java/src/main/java/com/pulumi/kubernetes/yaml/v2/ConfigGroup.java

@@ -23,6 +23,39 @@
  * 3. Using a literal string containing YAML, or a list of such strings:
  * 4. Any combination of files, patterns, or YAML strings:
  * 
+ * ## Dependency ordering
+ * Sometimes resources must be applied in a specific order. For example, a namespace resource must be
+ * created before any namespaced resources, or a Custom Resource Definition (CRD) must be pre-installed.
+ * 
+ * Pulumi uses heuristics to determine which order to apply and delete objects within the ConfigGroup.  Pulumi also
+ * waits for each object to be fully reconciled, unless `skipAwait` is enabled.
+ * 
+ * ### Explicit Dependency Ordering
+ * Pulumi supports the `config.kubernetes.io/depends-on` annotation to declare an explicit dependency a given resource.
+ * The annotation accepts a list of resource references, delimited by commas.
+ * 
+ * Note that references to resources outside the ConfigGroup aren't supported.
+ * 
+ * **Resource reference**
+ * 
+ * A resource reference is a string that uniquely identifies a resource.
+ * 
+ * It consists of the group, kind, name, and optionally the namespace, delimited by forward slashes.
+ * 
+ * | Resource Scope   | Format                                         |
+ * | :--------------- | :--------------------------------------------- |
+ * | namespace-scoped | `<group>/namespaces/<namespace>/<kind>/<name>` |
+ * | cluster-scoped   | `<group>/<kind>/<name>`                        |
+ * 
+ * For resources in the “core” group, the empty string is used instead (for example: `/namespaces/test/Pod/pod-a`).
+ * 
+ * ### Ordering across ConfigGroups
+ * The `dependsOn` resource option creates a list of explicit dependencies between Pulumi resources.
+ * Make another resource dependent on the ConfigGroup to wait for the resources within the group to be deployed.
+ * 
+ * A best practice is to deploy each application using its own ConfigGroup, especially when that application
+ * installs custom resource definitions.
+ * 
  * ## Example Usage
  * {% /examples %}}
  * 

sdk/nodejs/yaml/v2/configFile.ts

@@ -7,6 +7,39 @@ import * as utilities from "../../utilities";
 /**
  * ConfigFile creates a set of Kubernetes resources from a Kubernetes YAML file.
  *
+ * ## Dependency ordering
+ * Sometimes resources must be applied in a specific order. For example, a namespace resource must be
+ * created before any namespaced resources, or a Custom Resource Definition (CRD) must be pre-installed.
+ *
+ * Pulumi uses heuristics to determine which order to apply and delete objects within the ConfigFile.  Pulumi also
+ * waits for each object to be fully reconciled, unless `skipAwait` is enabled.
+ *
+ * ### Explicit Dependency Ordering
+ * Pulumi supports the `config.kubernetes.io/depends-on` annotation to declare an explicit dependency a given resource.
+ * The annotation accepts a list of resource references, delimited by commas.
+ *
+ * Note that references to resources outside the ConfigFile aren't supported.
+ *
+ * **Resource reference**
+ *
+ * A resource reference is a string that uniquely identifies a resource.
+ *
+ * It consists of the group, kind, name, and optionally the namespace, delimited by forward slashes.
+ *
+ * | Resource Scope   | Format                                         |
+ * | :--------------- | :--------------------------------------------- |
+ * | namespace-scoped | `<group>/namespaces/<namespace>/<kind>/<name>` |
+ * | cluster-scoped   | `<group>/<kind>/<name>`                        |
+ *
+ * For resources in the “core” group, the empty string is used instead (for example: `/namespaces/test/Pod/pod-a`).
+ *
+ * ### Ordering across ConfigFiles
+ * The `dependsOn` resource option creates a list of explicit dependencies between Pulumi resources.
+ * Make another resource dependent on the ConfigFile to wait for the resources within the group to be deployed.
+ *
+ * A best practice is to deploy each application using its own ConfigFile, especially when that application
+ * installs custom resource definitions.
+ *
  * ## Example Usage
  * ### Local File
  *

sdk/nodejs/yaml/v2/configGroup.ts

@@ -13,6 +13,39 @@ import * as utilities from "../../utilities";
  * 3. Using a literal string containing YAML, or a list of such strings:
  * 4. Any combination of files, patterns, or YAML strings:
  *
+ * ## Dependency ordering
+ * Sometimes resources must be applied in a specific order. For example, a namespace resource must be
+ * created before any namespaced resources, or a Custom Resource Definition (CRD) must be pre-installed.
+ *
+ * Pulumi uses heuristics to determine which order to apply and delete objects within the ConfigGroup.  Pulumi also
+ * waits for each object to be fully reconciled, unless `skipAwait` is enabled.
+ *
+ * ### Explicit Dependency Ordering
+ * Pulumi supports the `config.kubernetes.io/depends-on` annotation to declare an explicit dependency a given resource.
+ * The annotation accepts a list of resource references, delimited by commas.
+ *
+ * Note that references to resources outside the ConfigGroup aren't supported.
+ *
+ * **Resource reference**
+ *
+ * A resource reference is a string that uniquely identifies a resource.
+ *
+ * It consists of the group, kind, name, and optionally the namespace, delimited by forward slashes.
+ *
+ * | Resource Scope   | Format                                         |
+ * | :--------------- | :--------------------------------------------- |
+ * | namespace-scoped | `<group>/namespaces/<namespace>/<kind>/<name>` |
+ * | cluster-scoped   | `<group>/<kind>/<name>`                        |
+ *
+ * For resources in the “core” group, the empty string is used instead (for example: `/namespaces/test/Pod/pod-a`).
+ *
+ * ### Ordering across ConfigGroups
+ * The `dependsOn` resource option creates a list of explicit dependencies between Pulumi resources.
+ * Make another resource dependent on the ConfigGroup to wait for the resources within the group to be deployed.
+ *
+ * A best practice is to deploy each application using its own ConfigGroup, especially when that application
+ * installs custom resource definitions.
+ *
  * ## Example Usage
  * ### Local File
  *