<li>New endpoints included in new release 18 with new logic.</li>
<li>New logic to support <strong><em>Vendor Extensibility</em></strong> on Publish Service.</li>
<li>New logic to support <strong><em>API Status</em></strong> feature on Publish and Events Services.</li>
<li>Supported Features now are mandatory for all POST and PUT Requests as is described on TS 29.222.<ul>
<li><strong>Possible Breaking change</strong>, all POST request now must include supported features attribute, default can me set to "0" to keep all features inactive.</li>
<li><strong>Possible Breaking change</strong> on Events API, if you need eventDetails information on notification you must activate <strong>Enhanced Event Report</strong> feature by setting properly the supported features flag.</li>
<h4id="api-status-feature"><strong>Api Status feature</strong></h4>
<ul>
<li>Events API:<ul>
<li>Event internal notifications between services improved to accomplish specification.</li>
<li>On event subscription <strong>SupportedFeatures</strong> is readed and stored in db to accomplish specification.</li>
<li>Also <strong>SupportedFeatures</strong> is checked before send event notification, in order to accomplish specification, sending <strong>eventDetails</strong> and related information according to <strong><em>enhanced_event_report</em></strong> and <strong><em>apiStatusMonitoring</em></strong> supported features activated.</li>
</ul>
</li>
</ul>
<h4id="issues"><strong>Issues</strong></h4>
<ul>
<li>Solved issue to get ready REDIS on deployment: REDIS scheduled on start to allow receive notification since service is deployed.</li>
<li>Solved problem removing service APIs published is provider register more than one APF.</li>
<li>Solved Superadmin problem deleting service API published through helper service if provider is not present.</li>
<li>Increased the overall stability, fixing some corner cases.</li>
<li>Location headers now are filled in same way at all services that needs it.</li>
<li>Security issues solved.</li>
<li>Base docker images present on ETSI registry.</li>
<li>Robot image uploaded to ETSI Registry.</li>
</ul>
<h4id="local-scripts">Local Scripts</h4>
<ul>
<li>All scripts were reviewed and improved.</li>
<li>New scripts to manage users on local deployment added:</li>
<li>create_users.sh: helps developer to create new users in local deployment.</li>
<li>remove_users.sh: helps developer to remove users from db in local deployment.</li>
</ul>
<h4id="remote-scripts">Remote Scripts</h4>
<p>New scripts developed to help on remote deployment, configuration and testing. All this script are stored under helm/scripts in capif repository.</p>
<p><strong><em>variables.sh</em></strong> contains all configuration that will be used on remote operation. This file must be filled carefully before run remote scripts.</p>
<ul>
<li>
<p>Deployment Scripts:</p>
<ul>
<li><strong><em>install_vault.sh</em></strong>: Deploy Vault component from k8s cluster, only needed if vault is not previously deployed. If it’s deployed you can setup vault token on variables.sh.</li>
<li><strong><em>install_monitoring.sh</em></strong>: Deploy monitoring on k8s cluster.</li>
<li><strong><em>install_capif.sh</em></strong>: Deploy OpenCAPIF on k8s cluster. It will be deployed on configured namespace with domain and hostnames configured under variables.sh.</li>
<li><strong><em>uninstall_vault.sh</em></strong>: Rollback Vault component from k8s cluster.</li>
<li><strong><em>uninstall_monitoring.sh</em></strong>: Rollback monitoring components from k8s cluster.</li>
<li><strong><em>uninstall_capif.sh</em></strong>: Rollback OpenCAPIF from k8s cluster.</li>
</ul>
</li>
<li>
<p>Manage remote users:</p>
<ul>
<li><strong><em>create_remote_users.sh</em></strong>: This script create users setup by parameters on deployed OpenCAPIF. Those users are created by administrator.</li>
<li><strong><em>remove_remote_users.sh</em></strong>: This script removes user from deployed OpenCAPIF.</li>
<li><strong><em>remove_remote_users_by_prefix.sh</em></strong>:: This script removes users by prefix.</li>
</ul>
</li>
<li>
<p>Configuration of bastion machine, this simplify DNS fixed resolution:</p>
<ul>
<li><strong><em>get_ingress.sh</em></strong>: This create a configuration for dns fixed resolution for ingress configured in namespace passed by parameters.</li>
<li><strong><em>set_ingress.sh</em></strong>: This scripts adds to /etc/hosts the fixed DNS resolution for ingress setup for namespace passed by parameters.</li>
</ul>
</li>
<li>
<p>Execute robot tests over remote deployment.</p>
<ul>
<li><strong><em>run_remote_capif_tests.sh</em></strong>: This scripts launch Robot Test docker image on current machine to reach deployed OpenCAPIF. Is useful to launch with “--include smoke” in order to ensure all is deployed properly.</li>
</ul>
</li>
<li>
<p>Just for testing, next scripts upload dummy information to deployed OpenCAPIF:</p>
<ul>
<li><strong><em>populate_create_remote_dummy_users.sh</em></strong>: : Create Dummy providers and invokers, publish service APIs and creates security context for invokers.</li>
<li><strong><em>populate_remove_remote_dummy_users.sh</em></strong>: Remove dummy information created.</li>
<h4id="new-test-included-on-documentation">New test included on documentation</h4>
<ul>
<li>New Vendor Extensibility test suite with 9 tests. <ahref="../testing/testplan/vendor_extensibility/">Api Events Service</a></li>
<li>New <ahref="../testing/testplan/api_status/">API Status feature</a> test suite.</li>
<li>Improved <ahref="../testing/testplan/api_events_service/">Events test suite</a> with 8 new tests.</li>
<li>Test plan updated with default supported features for all request set to "0" (all inactive by default) <ahref="../testing/testplan/common_operations/">See common operations</a>.</li>