...
Transformations can be created, but not altered at this time.
Ordering issue
Partial Deploy Grants - testing on fdglp01 now, but looks like it is working
Grants to objects other than Tables - should test them as well.
...
Grants to objects that are renamed?
Remove Should we just remove Job support from this release? Job schedule and Job Program support is added in this release. Select the Job object type to build and deploy them. Actual Jobs are not supported due to date issues.
Source:
Wed Jul 18 13:57:19 CDT 2018 - 1 - INFO - flexagon.fd.plugin.core.utils.FlexSqlUtils.executeFlexSqlFile - Executing SQL statement:
[BEGIN
DBMS_SCHEDULER.CREATE_JOB (
job_name => 'AT_P12_1531940235144.UPDATE_SALES',
job_type => 'STORED_PROCEDURE',
job_action => 'AT_P12_1531940235144.UPDATE_SALES_SUMMARY',
start_date => '28-APR-08 07.00.00 PM Australia/Sydney',
repeat_interval => 'FREQ=DAILY;INTERVAL=2', /* every other day */
end_date => '20-NOV-08 07.00.00 PM Australia/Sydney',
auto_drop => FALSE,
comments => 'My new job');
END;]
SQL executed successfully.
Baseline fails with error:
Wed Jul 18 13:57:21 CDT 2018 - 1 - SEVERE - flexagon.ff.common.core.exceptions.FlexCheckedException.init() - java.sql.SQLDataException: ORA-01843: not a valid month
flexagon.ff.common.core.exceptions.FlexCheckedException: java.sql.SQLDataException: ORA-01843: not a valid month
at flexagon.fd.plugin.database.utils.FlexRunSQLHelper.executeCreateBaseline(FlexRunSQLHelper.java:323)
at flexagon.fd.plugin.database.utils.FlexRunBaseline.runBaseline(FlexRunBaseline.java:512)
at flexagon.fd.plugin.database.operations.FlexOracleDBCreateBaseline.execute(FlexOracleDBCreateBaseline.java:92)
That is why it is commented.
Maybe it is best to just comment out Jobs entirely and remove it from the project property for now?
Transformations - These are counted as queues currently. Probably should add a new output for them. - I added a new output store for them, but I didn't put it in the plugin.xml and map it out. I can do that if we want to.
All customers will drop fddb schema and recreate it. All prior builds will be in an unusable state, and shouldn't be reused.
...