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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update some names for registry #11506
Conversation
Changelog[uncommitted] (2022-12-03) |
Signed-off-by: susanev <susan.ra.evans@gmail.com>
// All custom resources have an implicit `id` output property, that we must inject into the docs. | ||
if !r.IsComponent { | ||
filteredOutputProps = append(filteredOutputProps, &schema.Property{ | ||
Name: "id", | ||
Comment: "The provider-assigned unique ID for this managed resource.", | ||
Type: schema.StringType, | ||
}) | ||
} | ||
// All resources have an implicit `id` output property, that we must inject into the docs. | ||
filteredOutputProps = append(filteredOutputProps, &schema.Property{ | ||
Name: "id", | ||
Comment: "The provider-assigned unique ID for this managed resource.", | ||
Type: schema.StringType, | ||
}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change needs to be removed from this PR. We should not be including the id
property for components. I just recently fixed this in #11469
type fs map[string][]byte | ||
|
||
func (fs fs) add(path string, contents []byte) { | ||
_, has := fs[path] | ||
contract.Assertf(!has, "duplicate file: %s", path) | ||
fs[path] = contents | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, all the rest of the changes related to fs
(including the need to import the contract
package at the top of the file) should be removed from this PR. This was a deliberate change in #11312 that shouldn't be reverted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@justinvp I could use your help on Monday. all of these came from what I thought was the right gen command to run, which was obviously wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well nevermind, i started over and its clean, going to close this in favor of #11525
fixing up some names for regsitry for seo and usability reasons