Releases: manifoldco/grafton
Releases · manifoldco/grafton
v0.8.0
Added
- The grafton client now returns
grafton.Error
if the received response
conforms to the responses expected in theprovider.yaml
swagger
specification. - The main
grafton
package now exports a functionIsFatal
which returns
whether or not an error is considered to be fatal to a provision, plan
change, or deprovisioning flow.
v0.7.0
Added
- The main
grafton
package now exports a functionCreateSsoURL
for deriving
an SSO URL.
v0.6.6
Fixed
- A backwards incompatible change was accidently introduced in
v0.6.5
,/v1
would always be appended to the url, instead,/v1
will only be appended if
the provided url does not end with/v1
.
v0.6.5
Fixed
- If a trailing slash is provided for the base url, Grafton will no longer
generate urls with duplicate/
between path segments. - Update README to include working example using
grafton test
/v1
will always be appended to the base url given to Grafton
v0.6.4
Fixed
- A resource can now be queried during the provisioning flow instead of after
it's completed.
v0.6.3
v0.6.2
Added
- Initial release from our public git repository.
- Detect, display, and fail on invalid status code responses during grafton
test.
Removed
- The credentials flag on grafton test, which was not used, has been removed.
Fixed
- Correct the RunsInside logic, so dependent features are not run when an outer
feature fails. - Display cleaner error messages when grafton fails to connect to your provider
implementation. - Handle and report on missing
message
fields in provider responses.