Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

pDNS documention correction for CR forwarding rule. #4695

Merged
merged 13 commits into from
Jul 20, 2023

Conversation

gahlaut-rahul
Copy link
Contributor

Community Note

  • Please vote on this pull request by adding a 馃憤 reaction to the original pull request comment to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Relates OR Closes #0000

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccXXX'

...

It has been observe, we need to correct our documentation for CR forwarding rule resources. CR forwarding rule type should be zone only while hostname is wrongly mentioned in valid options for type.

This PR is to correct the documentation for pDNS.

@@ -74,7 +74,7 @@ Review the argument reference that you can specify for your resource.
* `resolver_id` - (Required, String) The unique identifier of a custom resolver.
* `description` - (Optional, String) Descriptive text of the forwarding rule.
* `type` - (Optional, String) Type of the forwarding rule.
* Constraints: Allowable values are: `zone`, `hostname`,`Default`.
* Constraints: Allowable values is: `zone`.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be

Constraints: Allowable value is: zone.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You mean it should not be in single quote. Is it so?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed it @sheltons . Please approve it now.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The quotes are fine. It's the agreement between singular "Allowable value is" or plural "Allowable values are".

@hkantare hkantare merged commit 0a834c0 into IBM-Cloud:master Jul 20, 2023
2 checks passed
@@ -74,7 +74,7 @@ Review the argument reference that you can specify for your resource.
* `resolver_id` - (Required, String) The unique identifier of a custom resolver.
* `description` - (Optional, String) Descriptive text of the forwarding rule.
* `type` - (Optional, String) Type of the forwarding rule.
* Constraints: Allowable values are: `zone`, `hostname`,`Default`.
* Constraints: Allowable values is: zone.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add the quotes back in, and change "values" to "value".

  • Constraints: Allowable value is: zone.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think, It got merged. I'll do it with new request. :) .

omaraibrahim pushed a commit to omaraibrahim/terraform-provider-ibm that referenced this pull request Jul 20, 2023
* Enabled argument updated in docs for PDNS glb resource

* reverting the change made to main branch wrongly

* Document correction for CR forwarding rule type

* Corrected documentation for forwarding rule type value
benbuchanan pushed a commit to benbuchanan/terraform-provider-ibm that referenced this pull request Aug 17, 2023
* Enabled argument updated in docs for PDNS glb resource

* reverting the change made to main branch wrongly

* Document correction for CR forwarding rule type

* Corrected documentation for forwarding rule type value
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants