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
a) add nickname support for both marketplace and services - this will replace the need for a hash when deploying a "multi" nature service;
b) allow for placeholders on marketplace "mapping" and "services" manifest field, such as %nickname% so the nickname of a marketplace item may be used as a nickname for a service OR mapping;
c) allow for objects/struct on marketplace "services" field just like we do for the "mapping" field. The user may provide "serviceName:version" or a "{serviceName: string, version: string, startupFile: string [...]}" format;
d) add "enable-https-redirect" on mapping creation and on service installation (only usable when auto-create-mapping is true);
The text was updated successfully, but these errors were encountered:
a) add nickname support for both marketplace and services - this will replace the need for a hash when deploying a "multi" nature service;
b) allow for placeholders on marketplace "mapping" and "services" manifest field, such as %nickname% so the nickname of a marketplace item may be used as a nickname for a service OR mapping;
c) allow for objects/struct on marketplace "services" field just like we do for the "mapping" field. The user may provide "serviceName:version" or a "{serviceName: string, version: string, startupFile: string [...]}" format;
d) add "enable-https-redirect" on mapping creation and on service installation (only usable when auto-create-mapping is true);
The text was updated successfully, but these errors were encountered: