Known Issues

Topic	Description
API Namespace creation	Currently it is only supported to create an API Namespace from scratch. The other two possibilities will be introduced in a later release and are disabled in the current version.
API Integration – IBM API Connect	The current version will not support an integration to IBM API Connect. The Feature will be introduced in a later release and is disabled in the current version.
Fetching permissions	When getting new permissions or when permissions are changed in Repository Membership or in Role Mapping, it may take up to 3 minutes (MAX) for them to get activated in the case of repository membership being changed. If the Role Mappings are changed then you should log out and log in again to activate the permissions. At the moment this time period is not configurable. In order to shorten the time needed to activate the new permissions, you can clear the cache manually by calling the corresponding API, e.g. through the Swagger UI interface.
Warnings shown in Commit and Push Action	In addition to the problems within a solution the validation also shows warnings as errors. In case there are only warnings (compare with Problems view) we recommend to use 'Force commit' to proceed.
Discriminator property for oneOf schemas	When creating a oneOf schema and setting a discriminator, a required property is created with the discriminator name and it is automatically attached to each schema that belongs in the oneOf schema. Therefore, when any of these schemas are used independently, then the discriminator property must be set accordingly to '#/components/schemas/<schema_localIdentifier>'.
Defining the discriminator property	If any of the schemas of a oneOf schema have the a property with the same name as the discriminator name, then the property of the schema will be replaced with the discriminator. The discriminator is an enum value of type String. Therefore, make sure there are no properties in any of the schemas of a oneOf schema with the prporty name the name of the discriminator while creating a oneOf schema.
Working with two developers on one solution	In case of conflicts, delete the `package-lock.json` of the solution and execute `fss pull`.
Trace logging	If Trace log level is configured logs might contain sensitive user information such as ID Token.
Unmasked Password using GitBash	By using GitBash with Windows the password during the fss setup is not masked. See also recommendation for tools to be used.
Indent not working in Documentation Editor	In WYSIWYG: Button is doing nothing in Markdown mode: Button seems to work but if one saves the content the indent is gone
Pods and jobs are crashing after installation	The communication to the kubernetes API within running java based pods cannot be established, because of a misplaced behaviour in recognizing the version of the underlying http protocol.
Auto Deploy does not work for GitHub Enterprise	When GitHub Enterprise is used as Git provider, the automatic triggering of a pipeline when pushing to a git repository won't work.

Topic

Description

API Namespace creation

Currently it is only supported to create an API Namespace from scratch. The other two possibilities will be introduced in a later release and are disabled in the current version.

API Integration – IBM API Connect

The current version will not support an integration to IBM API Connect. The Feature will be introduced in a later release and is disabled in the current version.

Fetching permissions

When getting new permissions or when permissions are changed in Repository Membership or in Role Mapping, it may take up to 3 minutes (MAX) for them to get activated in the case of repository membership being changed. If the Role Mappings are changed then you should log out and log in again to activate the permissions. At the moment this time period is not configurable. In order to shorten the time needed to activate the new permissions, you can clear the cache manually by calling the corresponding API, e.g. through the Swagger UI interface.

Warnings shown in Commit and Push Action

In addition to the problems within a solution the validation also shows warnings as errors. In case there are only warnings (compare with Problems view) we recommend to use 'Force commit' to proceed.

Discriminator property for oneOf schemas

When creating a oneOf schema and setting a discriminator, a required property is created with the discriminator name and it is automatically attached to each schema that belongs in the oneOf schema. Therefore, when any of these schemas are used independently, then the discriminator property must be set accordingly to '#/components/schemas/<schema_localIdentifier>'.

Defining the discriminator property

If any of the schemas of a oneOf schema have the a property with the same name as the discriminator name, then the property of the schema will be replaced with the discriminator. The discriminator is an enum value of type String. Therefore, make sure there are no properties in any of the schemas of a oneOf schema with the prporty name the name of the discriminator while creating a oneOf schema.

Working with two developers on one solution

In case of conflicts, delete the package-lock.json of the solution and execute fss pull.

Trace logging

If Trace log level is configured logs might contain sensitive user information such as ID Token.

Unmasked Password using GitBash

By using GitBash with Windows the password during the fss setup is not masked. See also recommendation for tools to be used.

Indent not working in Documentation Editor

In WYSIWYG: Button is doing nothing
in Markdown mode: Button seems to work but if one saves the content the indent is gone

Pods and jobs are crashing after installation

The communication to the kubernetes API within running java based pods cannot be established, because of a misplaced behaviour in recognizing the version of the underlying http protocol.

Auto Deploy does not work for GitHub Enterprise

When GitHub Enterprise is used as Git provider, the automatic triggering of a pipeline when pushing to a git repository won't work.