You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have the mkdir method at least for the lowest level, the container because it seems container are not created on the fly when a mapper is used. If the container testtzis does not exist in the following account, the mapper runs into an error:
Yes, implementing mkdir and rmdir on containers should be straight forward (I'd consider it the second level though, because there are accounts as well. We'd need (from the SWIFT API):
PUT /v1/{account}/{container} for mkdir
DELETE /v1/{account}/{container} for rmdir
I'd probably even go one step further (maybe in another PR) and also catch the error you describe. Then create the container and redo the request. We might want to make this optional though...
I might not be able to that change very soon, but PR's are welcome.
It would be nice to have the
mkdir
method at least for the lowest level, the container because it seems container are not created on the fly when a mapper is used. If the containertesttzis
does not exist in the following account, the mapper runs into an error:Do you think that is possible?
The text was updated successfully, but these errors were encountered: