Skip to content

Commit

Permalink
[ignore] Change description of ACI_ALLOW_EXISTING_ON_CREATE provider …
Browse files Browse the repository at this point in the history
…flag
  • Loading branch information
akinross committed Jul 3, 2024
1 parent 0e6e6b5 commit db242cb
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion docs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -145,4 +145,4 @@ NOTE: either 'password' OR 'private_key' and 'cert_name' must be provided for th

~> The existence of an object in APIC can only be verified when the distinguished name (DN) can be constructed during plan. The verification <b>cannot</b> take place when a `parent_dn` attribute or any of the `naming` attributes ( attributes that are required to construct the DN ) of a resource are unknown ( known after apply ) during plan. An example of a unknown attribute input would be to use a DN reference ( `aci_tenant.example.id` ) to a resource that is being configured in the same plan. The DN of the object <b>cannot</b> be determined prior to apply and thus the existence of the object in APIC <b>cannot</b> be verified during plan. In these cases the verification will be performed during the apply operation.

-> Disabling this flag will suppress an additional API call during the plan phase for newly defined resources in the configuration.
-> Disabling this flag will add an API call during the plan phase for newly defined resources in the configuration.
2 changes: 1 addition & 1 deletion gen/templates/index.md.tmpl
Original file line number Diff line number Diff line change
Expand Up @@ -128,4 +128,4 @@ NOTE: either 'password' OR 'private_key' and 'cert_name' must be provided for th

~> The existence of an object in APIC can only be verified when the distinguished name (DN) can be constructed during plan. The verification <b>cannot</b> take place when a `parent_dn` attribute or any of the `naming` attributes ( attributes that are required to construct the DN ) of a resource are unknown ( known after apply ) during plan. An example of a unknown attribute input would be to use a DN reference ( `aci_tenant.example.id` ) to a resource that is being configured in the same plan. The DN of the object <b>cannot</b> be determined prior to apply and thus the existence of the object in APIC <b>cannot</b> be verified during plan. In these cases the verification will be performed during the apply operation.

-> Disabling this flag will suppress an additional API call during the plan phase for newly defined resources in the configuration.
-> Disabling this flag will add an API call during the plan phase for newly defined resources in the configuration.

0 comments on commit db242cb

Please sign in to comment.