Closed vitoravelino closed 6 years ago
@MaximilianMeister I copied from the issue that was probably out of sync compared to the gdocs that was reviewed by docs team. Now looks good I guess.
That looks awesome :clap:
@mjura please take a look at the description and make sure they still make sense.
Can we agree that this is the format for all input pages in the future? If so are there some Velum development guidelines where this could be added? I like the way this works and how much information there is to guide the user.
And @vitoravelino Could you please add an updated screenshot of this page here or send me one once this has been merged?
Thanks
Can we agree that this is the format for all input pages in the future?
I think so. Unless we have a completely redesign, we should keep favoring this kind of approach.
And @vitoravelino Could you please add an updated screenshot of this page here or send me one once this has been merged?
Will do.
Blog post was updated, can you please once again update screens there are already some new changes.
Rebased with the recent merges and updated the main screenshot. Reviews are welcome! :wink:
Travis and Jenkins are green. Once we approve this we can merge it. And then I'll be able to provide a backport for it.
The OpenStack API fields didn't have any additional information about them and no indicator of which fields were required or not for a valid configuration.
Fixes bsc#1097817
Signed-off-by: Vítor Avelino vavelino@suse.com